Contrast Media Injection Data Management System

ABSTRACT

Contrast administration data that relates to operation of a contrast media injector system ( 602 ) may be converted from at least one format (e.g., a CAN-compliant format) to at least one other format (e.g., an HL-7-compliant format) for use by a medical system ( 600 ). Data on contrast media prescribed for an imaging operation using an imaging system ( 690 ), data on contrast media dispensed from a contrast media storage/dispensing unit ( 500 ) for use in this imaging operation, and data on contrast media actually administered/injected by a contrast media injector system ( 602 ) for this imaging operation may be stored in a data structure ( 780 ). Patient renal function data may be used to control the dispensing of contrast media from the contrast media/storage/dispensing unit ( 500 ), to control the operation of the contrast media injector system ( 602 ), or both, and may be stored in the data structure ( 780 ) as well.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a non-provisional patent application of, andclaims priority to, pending U.S. Provisional Patent Application Ser. No.61/483,816, that is entitled “CONTRAST MEDIA INJECTION DATA MANAGEMENTSYSTEM,” and that was filed on May 9, 2011.

FIELD OF THE INVENTION

The present invention generally relates to the field of contrastmedia/agents and, more particularly, to managing contrast mediainjection/administration data.

BACKGROUND

Various medical procedures require that one or more medical fluids beinjected into a patient. For example, medical imaging proceduresoftentimes involve the injection of contrast media into a patient,possibly along with saline and/or other fluids. Power injectors may beused for these types of injections.

A power injector generally includes what is commonly referred to as apowerhead. One or more syringes may be mounted to the powerhead invarious manners (e.g., detachably; rear-loading; front-loading;side-loading). Each syringe typically includes what may be characterizedas a syringe plunger, piston, or the like. Each such syringe plunger isdesigned to interface with (e.g., contact and/or temporarilyinterconnect with) an appropriate syringe plunger driver that isincorporated into the powerhead, such that operation of the syringeplunger driver axially advances the associated syringe plunger insideand relative to a barrel of the syringe. One typical syringe plungerdriver is in the form of a ram that is mounted on a threaded lead ordrive screw. Rotation of the drive screw in one rotational directionadvances the associated ram in one axial direction, while rotation ofthe drive screw in the opposite rotational direction advances theassociated ram in the opposite axial direction.

Patient safety is of course of paramount concern when injecting contrastmedia into a patient. One such safety concern is whether a patient'sorgans can reasonably tolerate the proposed volume and/or concentrationof contrast media (e.g., amount and/or concentration of iodine in atleast certain computed tomography contrast medias) to be injected. Inthis regard, a patient's kidney(s) should be functioning at a level soas to clear the contrast media from the patient's bloodstream within acertain amount of time to avoid undesirable health risks (e.g., damagingthe patient's kidney(s) and/or other organs). For example, injections ofcertain concentrations and volumes of contrast media may adverselyimpact the health of some patients due to their compromised kidneyfunction.

SUMMARY

A first aspect of the present invention is embodied by a contrast mediainjector system that includes a powerhead, a syringe, a reader, and arenal function assessment module. The powerhead includes a housing, amotorized drive ram, and a syringe mount (e.g., of any appropriate type,for instance, a removable faceplate or a syringe mount that is fixedlyattached to (e.g., integral with) the powerhead (e.g., the housingthereof)). The motorized drive ram of the powerhead is designed to movealong an axis, and at least part of the motorized drive ram is locatedwithin the housing. The syringe mount of the powerhead is designed to atleast substantially immobilize a barrel of the syringe relative to thehousing of the powerhead such that the drive ram can move a plunger ofthe syringe within and relative to the syringe barrel.

The syringe is installed on the powerhead (e.g., using the syringemount) in the case of the first aspect, and includes a data storagedevice that stores at least first threshold renal function data. Thereader is able to communicate with the syringe data storage device, forinstance to retrieve the first threshold renal function data for use bythe renal function assessment module. In this regard, the renal functionassessment module includes comparative logic that is configured tocompare the first threshold renal function data with renal function dataon a patient to be imaged.

A number of feature refinements and additional features are applicableto the first aspect of the present invention. These feature refinementsand additional features may be used individually or in any combinationin relation to the first aspect. As such, each of the following featuresthat will be discussed may be, but are not required to be, used with anyother feature or combination of features of the first aspect. Thefollowing discussion is separately applicable to the first aspect, up tothe start of the discussion of a second aspect of the present invention.

The contrast media injector system may utilize one or more data inputdevices of any appropriate type (e.g., a user input device). One or moredata input devices may be incorporated by the powerhead and/or a remoteconsole of the contrast media injector system. Any remote console of thecontrast media injector system may be in communication with thepowerhead, may include a remote console display, may include at leastone data input device, and/or may be in a different location (e.g.,isolated in at least some fashion) from the powerhead of the contrastmedia injector system. Any data input device incorporated by thecontrast media injector system may accommodate the provision of input(e.g., user input) to the contrast media injector system for anyappropriate purpose, including programming injection parameters (e.g.,to define an injection protocol having one or more phases, each phaseincluding injection parameters such as an amount of fluid to be injectedand an injection flow rate, as well as possibly one or more injectiondelays (sometimes referred to as “holds” and/or “pauses”), each of whichcan be of finite or infinite duration)). The contrast media injectorsystem could also accommodate data input from one or more external datainput devices (i.e., that are not actually part of the contrast mediainjector system), such as one or more data input devices associated withimaging equipment (e.g., a CT or MR scanner) or other parts of ahealthcare facility. A given data input device may be used to provideany appropriate data to the contrast media injector system, for instancerenal function data on a patient to be imaged and which may be used bythe renal function assessment module as will be discussed below.

One or more data input devices that are available to at leastcommunicate with the contrast media injector system each may be of anyappropriate type (e.g., keyboard, touch screen, mouse, joystick,trackball, and/or any combination thereof). Although any appropriateuser input may be provided to the contrast media injector system throughsuch a data input device, renal function data of a patient to be imagedmay be manually input to the contrast media injector system by a user.The contrast media injector system may include multiple data inputdevices. In one embodiment, one data input device is associated with aremote console associated with the contrast media injector system (e.g.,part of or at least co-located with the remote console in a control roomthat is separate/isolated from an imaging room having the powerhead andmedical imaging equipment), while another data input device isassociated with the powerhead (e.g., in the form of a touch screendisplay that is integrated with the powerhead).

Renal function data on a patient to be imaged in conjunction withoperation of the contrast media injector system may be acquired in anyappropriate manner and may be communicated to the contrast mediainjector system in any appropriate manner. Renal function data on apatient to be imaged may be input by a user to the contrast mediainjector system in any appropriate manner (e.g., manually entering datathat is representative of a patient's renal function; in the form ofuser input). Renal function data on a patient to be imaged may beacquired from one or more data sources that may be in communication orable to communicate with the contrast media injector system, such as ahospital information system (HIS), a radiology information system (RIS),picture archive and communication system (PACS), another system thatstores or has access to patient electronic medical records (EMRs), or arenal function testing module.

The renal function assessment module may include (or, in someembodiments, refers to) prompt logic that is configured to issue aprompt for entry of renal function information regarding a patient to beimaged (e.g., manually by a user through an appropriate data inputdevice). The renal function information that is the subject of theprompt may be data that is representative of the renal function of thepatient that is to be imaged (e.g., glomerular filtration rate or “GFR”,serum creatinine measurement, or any other appropriate renal functionindicator). In one embodiment, a first user input is provided to thecontrast media injector system in the form of first renal function dataof a first patient to be imaged, and the renal function assessmentmodule includes comparative logic that is configured to compare thefirst renal function data of the first patient with the first thresholdrenal function data. Both the first renal function data and the firstthreshold renal function data may be of any appropriate type so long asthe data is indicative of patient renal function (e.g., GFR, serumcreatinine measurement). For instance, the first renal function data ofthe first patient may be expressed in terms of a GRF measurement, andthe first threshold renal function data to which the first renalfunction data may be compared may also be in terms of a threshold GRF oran acceptable range of GFR. As another example, the first renal functiondata of the first patient may be expressed in terms of a serumcreatinine measurement, and the first threshold renal function data towhich the first renal function data may be compared may also be in termsof a threshold serum creatinine level or an acceptable range of serumcreatinine. The first threshold renal function data may be expressed inany appropriate manner (e.g., in the form of a baseline number, suchthat the first renal function data must be at least as great as thebaseline number or, in another embodiment, no greater than the baselinenumber; in the form of a range, such that the first renal function datamust be within this range).

An issued prompt for entry of patient renal function information may bepresented on at least one display of the contrast media injector system,for instance on a display associated with (e.g., incorporated by) thepowerhead, on a remote console display associated with the contrastmedia injector system, or both. A data input device may enable a user tomanually respond to the noted prompt for renal function information ofthe patient to be imaged. The prompt may be of any appropriate format,and may request the input of the desired renal function information inany appropriate manner. For instance, the prompt may be in the form of arequest for a user to provide/input the renal function information tothe contrast media injector system (e.g., for comparison with thresholdrenal function data). Any data that is representative of a patient'srenal function could be manually input through a user input device.

The prompt may simply be in the form of an inquiry directed todetermining if the renal function of a patient to be imaged has beendetermined to be acceptable (e.g., in relation to threshold renalfunction data). That is, it may be such that a user must simply confirmthat the patient's renal function has been checked and has beendetermined by the user (or other appropriate personnel) to comply withrelevant threshold renal function data (e.g., a “yes/no” or “pass/fail”question). In another embodiment, the prompt logic may be configured toissue a prompt (e.g., visually display a prompt to a user) requestingthat the user select an answer from a list of displayed answersregarding the patient to be imaged in conjunction with the operation ofthe contrast media injector system. In yet another embodiment, theprompt logic may be configured to issue a prompt (e.g., visually displaya prompt to a user) requesting that the user enter/fill in an empty datafield shown on a display of the system with renal function dataregarding the patient to be imaged in conjunction with the operation ofthe contrast media injector system.

In one embodiment, the contrast media injector system may be precludedfrom being operated to provide a contrast media discharge (e.g., so asto not allow for execution of an injection protocol) based upon the userinput provided in relation to the noted prompt. For instance, thecontrast media injector system may be configured so that the injectorsystem is precluded from being operated to provide a contrast mediadischarge (e.g., where at least one syringe plunger is advanced relativeto the corresponding syringe barrel by the contrast media injectorsystem) if the patient renal function data that is entered by a userdoes not comply with the first threshold renal function data. As anotherexample, the contrast media injector system may be configured so thatthe injector system is precluded from being operated to provide acontrast media discharge if the patient renal function data that isentered by a user does not “pass” an electronic evaluation conducted bythe renal function assessment module, which takes the first thresholdrenal function data stored on the data storage device of the syringeinto account when conducting the above-described evaluation. Thecontrast media injector system may be configured such that the injectorsystem is precluded from being operated to provide a contrast mediadischarge if the user does not respond to the prompt at all, if the userresponds in the negative to a request for verification that the renalfunction of a patient to be imaged has been determined to be acceptable,or both. The above-referenced preclusions of contrast media injectorsystem operation may include such things as not allowing the injectorsystem to “arm” or be “enabled” to run the programmed injectionprotocol. Additionally or alternatively, the above-referencedpreclusions of contrast media injector system operation may include suchthings as not allowing the user to initiate (e.g., “run” or “start”) theprogrammed injection protocol (e.g., if the system is allowed to be“armed”/“enabled” prior to an inquiry regarding patient renal function)and/or inject contrast media into the patient manually using one or morehand controls (e.g., buttons) of the injector system.

The renal function assessment module may include one or more processors.In one embodiment, one or more processors of the renal functionassessment module are located within and/or incorporated by thepowerhead of the contrast media injector system (e.g., one or moreprocessors of the renal function assessment module may be “on board” inrelation to the powerhead of the contrast media injector system). Inanother embodiment, one or more processors of the renal functionassessment module are located within and/or incorporated by a remoteconsole associated with the contrast media injector system. At least oneprocessor of the renal function assessment module (e.g., a firstprocessor) may be programmed: 1) to issue a prompt regarding renalfunction information for a patient to be imaged; 2) to preclude thecontrast media injector system from being operated to provide a contrastmedia discharge (e.g., disallow execution of an injection protocol) ifrenal function data on a patient to be imaged does not comply with firstthreshold renal function data (e.g., does not meet or exceed firstthreshold renal function data); 3) to issue an alarm of any appropriatetype or types (e.g., visual, audible) if patient renal function data ona patient to be imaged does not comply with first threshold renalfunction data (e.g., does not meet or exceed first threshold renalfunction data); 4) to generate next action instructions as to at leastone action to be taken if renal function data on a patient to be imageddoes not comply with first threshold renal function data (e.g., does notmeet or exceed first threshold renal function data); and/or 5) anycombination of two or more of the foregoing.

At least one syringe installed on the powerhead may include contrastmedia (e.g., CT or MR contrast media), and the first threshold renalfunction data stored on the data storage device of the syringe may referto threshold renal function data of the corresponding contrast media inthe syringe. Any other appropriate information may be stored on the datastorage device of the syringe, for instance the type (e.g., identity,chemical composition, active ingredient) of contrast media within thesyringe, the concentration (e.g., iodine content and/or level of anotheringredient) of the contrast media within the syringe, the volume ofcontrast media within the syringe, threshold (e.g., minimum) renalfunction data for a patient proposed to receive a predefined volume(e.g., 5 ml, 10 ml, 15, ml, 20 ml, 25 ml, 30 ml, 35 ml, 40 ml, 45 ml, 50ml, 55 ml, 60 ml, 65 ml, 70 ml, 75 ml, 80 ml, 85 ml, 90 ml, 95 ml, 100ml, 105 ml, 110 ml, 115 ml, 120 ml, 125 ml, 130 ml, 135 ml, 140 ml, 145ml, 150 ml, any of which may or may not be the entire volume of contrastmedia within the syringe) or the entire volume of contrast media withinthe syringe, or any combination thereof.

The reader associated with the contrast media injector system in thecase of the first aspect may be of any appropriate type, may beincorporated in any appropriate manner by the contrast media injectorsystem (e.g., on the powerhead, for instance where at least part of thisreader may be incorporated by the syringe mount of the powerhead), maybe configured to communicate with the syringe data storage device in anyappropriate manner (e.g., to read/retrieve data stored on the syringedata storage device), or any combination thereof. In one embodiment, thedata storage device of the syringe is in the form of an RF or RFID datatag(s), and the reader is in the form of an electromagnetic device(e.g., an RF antenna) that is configured to electromagnetically readdata from (and optionally write data to) the RF data tag(s) on thesyringe.

The contrast media injector system may include a data store thatincludes threshold renal function data for a plurality of contrast mediatypes (e.g., for a plurality of different contrast agents, where thedifference between two contrast media types may be in the form of havingdifferent concentrations of one or more contrast media constituents).The threshold renal function data for a particular contrast media typemay be characterized as “contrast media type-specific threshold renalfunction data.” Although each contrast media type may be associated witha particular threshold renal function, one or more contrast media typescould be associated with the same threshold renal function. However,each contrast media type could have a different threshold renal function(e.g., depending on the volume and/or concentration of the contrastmedia within the syringe). The data store may be of any appropriateconfiguration for purposes of associating a contrast media type withthreshold renal function data, for instance, in the form of a look-uptable. In one embodiment, identifying the contrast media type to thecontrast media injector system (e.g., through a data input device), andthat will be used for an injection (e.g., injected into a patient),results in the corresponding threshold renal function data beingautomatically retrieved from the data store (e.g., a lookup table) bythe contrast media injector system. It should be appreciated that a usercould also manually input the first threshold renal function data intothe contrast media injector system (e.g., through a user input devicefor the remote console, for the power injector, or both).

A second aspect of the present invention is embodied by a contrast mediainjector system that includes a powerhead and a data store. Thepowerhead includes a housing, a motorized drive ram, and a syringe mount(e.g., of any appropriate type, for instance, a faceplate or a syringemount that is fixedly attached to (e.g., integral with) the powerhead(e.g., the housing thereof)). The motorized drive ram of the powerheadis designed to move along an axis, and at least part of the motorizeddrive ram is located within the housing. The syringe mount of thepowerhead is designed to at least substantially immobilize a barrel of asyringe relative to the housing of the powerhead such that the drive ramcan move a plunger of this syringe within and relative to the syringebarrel. The data store of the injector system includes a plurality ofcontrast media types and their corresponding threshold renal function.

A number of feature refinements and additional features are applicableto the second aspect of the present invention. These feature refinementsand additional features may be used individually or in any combinationin relation to the second aspect. As such, each of the followingfeatures that will be discussed may be, but are not required to be, usedwith any other feature or combination of features of the second aspect.The following discussion is applicable to the second aspect, up to thestart of the discussion of a third aspect of the present invention.Initially, each feature set forth in relation to the first aspect may beutilized by this second aspect, and vice versa.

The threshold renal function or threshold renal function data for aparticular contrast media type (e.g. a minimum patient renal functionrequired/suggested for safe administration of the corresponding contrastmedia to the patient; a range of acceptable patient renal functionsrequired/suggested for safe administration of the corresponding contrastmedia to the patient) may be characterized as a “contrast mediatype-specific threshold renal function.” Although each contrast mediatype may be associated with a particular threshold renal function, oneor more contrast media types could be associated with the same thresholdrenal function (the data store may use relational data storagetechniques as desired). However, each contrast media type could have adifferent threshold renal function. The data store may be of anyappropriate configuration for purposes of associating a contrast mediatype with a threshold renal function, for instance, in the form of alook-up table. In one embodiment, identifying the contrast media type tothe contrast media injector system (e.g., through a data input device;through the reader discussed above in relation to the first aspect,which may read data from a data storage device on a syringe thatidentifies its contrast media type to the contrast media injectorsystem), and that will be used for an injection (e.g., injected into apatient), results in the corresponding threshold renal function beingautomatically retrieved from the data store (e.g., a lookup table) bythe contrast media injector system.

An appropriate computer-readable storage medium may be configured toinclude the data store utilized by this second aspect. The data storemay be incorporated by the contrast media injector system in anyappropriate manner. At least part of the data store may reside on thepowerhead, on a remote console of the contrast media injector system, onone or more components that are external to the contrast media injectorsystem (e.g., on an imaging system; on a hospital information system(HIS); on a radiology information system (RIS); on a picture archive andcommunication system (PACS), or any combination thereof).

A third aspect of the present invention is directed to controllingcontainers of contrast media. Consider the case where there is a supplyof a plurality of contrast media containers (e.g., within a contrastmedia storage/dispensing unit). A renal function check may be undertakenbefore releasing a particular contrast media container from the supply(e.g., for subsequent use by a contrast media injector system forexecuting an injection protocol where contrast media from the contrastmedia container is injected into a patient).

A number of feature refinements and additional features are applicableto the third aspect of the present invention. These feature refinementsand additional features may be used individually or in any combinationin relation to the third aspect. As such, each of the following featuresthat will be discussed may be, but are not required to be, used with anyother feature or combination of features of the third aspect. Thefollowing discussion is applicable to the third aspect, up to the startof a discussion of a fourth aspect of the present invention. Initially,the third aspect may be used in conjunction with each of the first andsecond aspects. Moreover, the third aspect may be implemented in anyappropriate manner, including in the form of a contrast media managementor dispensing system, as well as in the form of managing the dispensingor release of a contrast media container for subsequent use in aninjection procedure or the like.

The third aspect may be implemented in the form of a contrast mediamanagement or dispensing system. Such a system may include a contrastmedia storage/dispensing unit of any appropriate size, shape,configuration, and/or type (e.g., at least generally in the form of avending machine). This system may store a plurality of contrast mediacontainers of any appropriate type (e.g., in the form of a syringe,bottle, or vial). Each such contrast media container may be in a sealedcondition while being stored by the contrast media management system(e.g., such that its contents are isolated from its surroundingenvironment and/or such that its contents remain sterile), and mayremain in this sealed condition when released from the supply. Thesystem may implement a renal function check before allowing a particularcontrast media container to be removed from/dispensed by the system. Forinstance, the system may incorporate a data input device of anyappropriate type and in any appropriate manner. Depending upon the datathat is provided to the contrast media management system, a contrastmedia container may or may not be dispensed from or released by thesystem.

In one implementation of the third aspect, a user may be required toprovide input regarding whether or not the renal function of a patientto be imaged has been determined to be sufficient in relation to aparticular contrast media type being requested from the supply. Apositive response (e.g., a confirmation by a user that the patient'srenal function complies with a threshold patient renal functionsuggested/required to promote safe administration of the contrast media)may allow a container of the desired contrast media to be dispensed orreleased from the supply. Otherwise, the third aspect may be configuredsuch that a container of the desired contrast media type is not releasedfrom the supply (e.g., in the case where the patient's renal functiondoes not meet or exceed a threshold patient renal functionsuggested/required to promote safe administration of the contrastmedia).

In another implementation of the third aspect, data regarding renalfunction of a patient that is to receive the contrast media may beinput, as well data regarding the desired contrast media type to bereleased from the supply. This may entail, a user manually entering therelevant data (e.g., inputting data that is representative of thepatient's renal function; inputting a patient identifier that allows thepatient's most current renal function to be retrieved from one or moredata sources (e.g., utilizing a “hospital information system” or HIS);inputting the identification of the desired contrast media type), mayentail a user making an appropriate selection from a drop-down menu, orthe like. The patient's renal function may be compared with a thresholdrenal function of the requested contrast media type, and which may beidentified to the contrast media storage/dispensing unit in anyappropriate manner (e.g., by a user identifying the contrast media typeto the unit, and having the unit retrieve the threshold renal functionfrom the data store discussed above; by a user inputting the thresholdrenal function to the unit through a user input device). In the eventthat the input patient renal function complies with the threshold renalfunction of the requested contrast media type (e.g., meets or exceedsthis threshold renal function), a container of the desired contrastmedia type may be released from the supply. Otherwise, the third aspectmay be configured such that a container of the desired contrast mediatype will not be released from the supply.

The plurality of contrast media containers that define the supply forthe contrast media management system may be of any appropriate type. Inone embodiment, the contrast media management system stores a pluralityof prefilled syringes (syringes that have been filled or loaded by asupplier, and that are ultimately transported to an end user or end-usefacility; prefilled syringes are not loaded with contrast media by anend user or an end-use facility) that may be released from the contrastmedia management system only in response to an output from the renalfunction assessment module. After being released from the contrast mediamanagement system (and still in a sealed condition), a given contrastmedia container may then be used by a contrast media injector system,may be used to inject a patient with contrast media, or both.

Each of the plurality of contrast media containers may include a datastorage device of any appropriate type (e.g., an RF tag). Anyappropriate information may be stored on any data storage deviceutilized by any of the contrast media containers. A contrast media typeidentifier may be stored on a data storage device for a contrast mediacontainer, threshold renal function data may be stored on a data storagedevice for a syringe and that relates to the contrast media within thecontrast media container, or the like. The contrast media managementsystem may include a reader of any appropriate type to obtaininformation from the data storage device of each contrast mediacontainer within its supply.

Threshold renal function data associated with contrast media in eachcontrast media container for the contrast media management system may beretrieved in any appropriate manner. As noted above, threshold renalfunction data may be retrieved from a data storage device associatedwith a particular contrast media container. Another option is toretrieve contrast media type data from a data storage device associatedwith a particular contrast media container, and from this informationretrieve corresponding threshold renal function data in any appropriatemanner (e.g., via a communication by the contrast media managementsystem with a hospital information system (HIS), with a radiologyinformation system (RIS), with a picture archive and communicationsystem (PACS), with another system housing or having access toelectronic medical records (EMRs), or the like; via direct input by auser).

The renal function assessment module may utilize threshold renalfunction data for a contrast media container of a selected contrastmedia type to determine whether the contrast media container should bereleased from its supply. One or more data input devices may beoperatively connected with the renal function assessment module. Therenal function assessment module may include comparative logic that isconfigured to compare threshold renal function data with patient renalfunction data that has been input to the contrast media managementsystem to determine whether the corresponding contrast media containershould be released from its supply (e.g., to determine if the renalfunction data on a patient to be imaged complies with the thresholdrenal function data of the contrast media to be injected into thepatient).

A fourth aspect of the present invention is embodied by a medicalimaging system that includes an imaging unit (e.g., CT scanner having anx-ray source, or MRI scanner having a magnet), where the imaging unitincludes a renal function assessment module.

A number of feature refinements and additional features are applicableto the fourth aspect of the present invention. These feature refinementsand additional features may be used individually or in any combinationin relation to the fourth aspect. As such, each of the followingfeatures that will be discussed may be, but are not required to be, usedwith any other feature or combination of features of the fourth aspect.

The imaging system may utilize one or more data input devices of anyappropriate type (e.g., a user input device). For instance, one or moredata input devices may be incorporated by a remote console of theimaging system. Any remote console of the imaging system may include aremote console display, may include at least one data input device,and/or may be in a different location (e.g., isolated in at least somefashion) from the imaging unit of the imaging system (for instance,outside of an x-ray and/or RF-shielded room that houses the imagingunit). Any data input device incorporated by the imaging system mayaccommodate the provision of input (e.g., user input) to the imagingsystem for any appropriate purpose, including programming appropriateimaging parameters. The imaging system could also accommodate data inputfrom one or more external data input devices (i.e., that are notactually part of the imaging system), such as one or more data inputdevices associated with imaging equipment (e.g., a contrast mediainjector system), a renal function testing module, or other parts of ahealthcare facility (e.g., HIS, RIS, PACS, or any other system housingor having access to patient EMRs). A given data input device may be usedto provide any appropriate data to the imaging system, for instance,renal function data on a patient to be imaged and/or threshold renalfunction data (both of which may be used by the renal functionassessment module of the imaging system as will be discussed below).

The renal function assessment module may include (or, in someembodiments, refers to) prompt logic that is configured to issue aprompt for entry of renal function information regarding a patient to beimaged (e.g., manually by a user through an appropriate data inputdevice). The renal function information that is the subject of theprompt may be data that is representative of the renal function of thepatient that is to be imaged (e.g., glomerular filtration rate or “GFR”,serum creatinine measurement, or any other appropriate renal functionindicator). In one embodiment, a first user input is provided to theimaging system in the form of first renal function data of a firstpatient to be imaged, and the renal function assessment module includescomparative logic that is configured to compare the first renal functiondata of the first patient with threshold renal function data. Both thefirst renal function data and the threshold renal function data may beof any appropriate type so long as the data is indicative of patientrenal function (e.g., GFR, serum creatinine measurement). The thresholdrenal function data may be expressed in any appropriate manner (e.g., inthe form of a baseline number, such that the first renal function datamust be at least as great as the baseline number or, in anotherembodiment, no greater than the baseline number; in the form of a range,such that the first renal function data must be within this range).

An issued prompt for entry of patient renal function information may bepresented on at least one display of the imaging system, for instance,on a display associated with (e.g., incorporated by) a remote console ofthe imaging system. A data input device may enable a user to manuallyrespond to the noted prompt for renal function information of thepatient to be imaged. The prompt may be of any appropriate format, andmay request the input of the desired renal function information in anyappropriate manner. For instance, the prompt may be in the form of arequest for a user to provide/input the renal function information tothe imaging system (e.g., for comparison with threshold renal functiondata). Any data that is representative of a patient's renal functioncould be manually input through a data input device.

The prompt may simply be in the form of an inquiry directed todetermining if the renal function of a patient to be imaged has beendetermined to be acceptable (e.g., in relation to threshold renalfunction data). That is, it may be such that a user must simply confirmthat the patient's renal function has been checked and has beendetermined by the user (or other appropriate personnel) to comply withrelevant threshold renal function data (e.g., a “yes/no” or “pass/fail”question). In another embodiment, the prompt logic may be configured toissue a prompt (e.g., visually display a prompt to a user) requestingthat the user select an answer from a list of displayed answersregarding the patient to be imaged in conjunction with the operation ofthe imaging system. In yet another embodiment, the prompt logic may beconfigured to issue a prompt (e.g., visually display a prompt to a user)requesting that the user enter/fill in an empty data field shown on adisplay of the system with renal function data regarding the patient tobe imaged in conjunction with the operation of the imaging system.

The imaging system may be communicatively interconnected with a contrastmedia injector system (e.g., via an appropriate hardwire interface(e.g., CAN interface) or through an appropriate wireless connection). Insuch embodiments, the contrast media injector system may be precludedfrom being operated to provide a contrast media discharge (e.g., so asto not allow for execution of an injection protocol) based upon the userinput entered into the imaging system in relation to the noted prompt.For instance, the imaging system may be configured to preclude theinjector system from being operated to provide a contrast mediadischarge (e.g., where at least one syringe plunger is advanced relativeto a corresponding syringe barrel by the contrast media injector system)if the patient renal function data that is entered by a user into theimaging system does not comply with the relevant threshold renalfunction data. As another example, the imaging system may be configuredto preclude the injector system from being operated to provide acontrast media discharge if the patient renal function data that isentered by a user does not “pass” an electronic evaluation conducted bythe renal function assessment module, which may take threshold renalfunction data into account when conducting the above-describedevaluation. The imaging system may be configured to preclude theinjector system from being operated to provide a contrast mediadischarge if the user of the imaging system does not respond to theprompt at all, if the user of the imaging system responds in thenegative to a request for verification that the renal function of apatient to be imaged has been determined to be acceptable, or both. Theabove-referenced preclusions of contrast media injector system operationinitiated by the imaging system may include such things as not allowingthe injector system to “arm” or be “enabled” to run a programmedinjection protocol. Additionally or alternatively, the above-referencedpreclusions of contrast media injector system operation initiated by theimaging system may include such things as not allowing initiation (e.g.,“run” or “start”) of a programmed injection protocol (e.g., if theinjector system is allowed to be “armed”/“enabled” prior to an inquiryregarding patient renal function) and/or inject contrast media into thepatient manually using one or more hand controls (e.g., buttons) of theinjector system.

The renal function assessment module may include comparative logic thatis configured to compare threshold renal function data with renalfunction data on a patient to be imaged. Renal function data on apatient to be imaged in conjunction with operation of the noted contrastmedia injector system may be acquired in any appropriate manner and maybe communicated to the imaging system in any appropriate manner. Renalfunction data on a patient to be imaged may be input to the imagingsystem by a user in any appropriate manner (e.g., manually entering datathat is representative of a patient's renal function; in the form ofuser input). Renal function data on a patient to be imaged may beacquired from one or more data sources that may be in communication orable to communicate with the imaging system, such as a hospitalinformation system (HIS), a radiology information system (RIS), picturearchive and communication system (PACS), another system that stores orhas access to patient electronic medical records (EMRs), or a renalfunction testing module.

Threshold renal function data may refer to threshold renal function dataof the contrast media to be injected into a patient to be imaged, andmay be used by the renal function assessment module to control whethercontrast media should be injected into a patient to be imaged. Thresholdrenal function data may be input to the imaging unit from anyappropriate source or combination of sources. Threshold renal functiondata may be retrieved from a data storage device associated with asyringe to be used in an imaging procedure, and which may then betransmitted to the imaging unit in any appropriate manner. Anotheroption is to retrieve contrast media type data from a data storagedevice associated with at least one syringe to be used in an imagingprocedure, and from this information retrieve corresponding thresholdrenal function data in any appropriate manner (e.g., via a communicationby the imaging system with a hospital information system (HIS), with aradiology information system (RIS), with a picture archive andcommunication system (PACS), with another system housing or havingaccess to electronic medical records (EMRs), or the like). Thresholdrenal function information could also be provided to the imaging systemvia direct user input.

The imaging system may include a database or data store that includesthreshold renal function data for a plurality of contrast media types(e.g., for a plurality of different contrast agents, where thedifference between two contrast media types may be in the form of havingdifferent concentrations of one or more contrast media constituents).The threshold renal function data for a particular contrast media typemay be characterized as “contrast media type-specific threshold renalfunction data.” Although each contrast media type may be associated witha particular threshold renal function, one or more contrast media typescould be associated with the same threshold renal function. However,each contrast media type could have a different threshold renal function(e.g., depending on the volume and/or concentration of the contrastmedia within the syringe). The data store may be of any appropriateconfiguration for purposes of associating a contrast media type withthreshold renal function data, for instance, in the form of a look-uptable. In one embodiment, identifying the contrast media type to theimaging system (e.g., through a data input device), and that will beused for an injection (e.g., injected into a patient using aninterconnected contrast media injector system), results in thecorresponding threshold renal function data being automaticallyretrieved from the data store (e.g., a lookup table) by the imagingsystem. It should be appreciated that a user could also manually inputthe threshold renal function data into the imaging system (e.g., througha user input device for the remote console).

At least one syringe may be utilized by the above-noted contrast mediainjector system, and at least one such syringe may include anappropriate data storage device. Threshold renal function data may bestored on the data storage device of any such syringe and may refer tothreshold renal function data for the contrast media contained in thesyringe. Any other appropriate information may be stored on the datastorage device of the syringe, for instance the type (e.g., identity,chemical composition, active ingredient) of contrast media within thesyringe, the concentration (e.g., iodine content and/or level of anotheringredient) of the contrast media within the syringe, the volume ofcontrast media within the syringe, threshold (e.g., minimum) renalfunction data for a patient proposed to receive a predefined volume(e.g., 5 ml, 10 ml, 15, ml, 20 ml, 25 ml, 30 ml, 35 ml, 40 ml, 45 ml, 50ml, 55 ml, 60 ml, 65 ml, 70 ml, 75 ml, 80 ml, 85 ml, 90 ml, 95 ml, 100ml, 105 ml, 110 ml, 115 ml, 120 ml, 125 ml, 130 ml, 135 ml, 140 ml, 145ml, 150 ml, any of which may or may not be the entire volume of contrastmedia within the syringe) or the entire volume of contrast media withinthe syringe, or any combination thereof.

The renal function assessment module utilized by the fourth aspect mayinclude one or more processors. At least one processor of the renalfunction assessment module (e.g., a first processor) may beprogrammed: 1) to issue a prompt regarding renal function informationfor a patient to be imaged; 2) to preclude an interconnected contrastmedia injector system from being operated to provide a contrast mediadischarge (e.g., disallow execution of an injection protocol) if renalfunction data on a patient to be imaged does not comply with thresholdrenal function data (e.g., does not meet or exceed threshold renalfunction data); 3) to issue an alarm of any appropriate type or types(e.g., visual, audible) if patient renal function data on a patient tobe imaged does not comply with threshold renal function data (e.g., doesnot meet or exceed threshold renal function data); 4) to generate nextaction instructions as to at least one action to be taken if renalfunction data on a patient to be imaged does not comply with thresholdrenal function data (e.g., does not meet or exceed first threshold renalfunction data); and/or 5) any combination of two or more of theforegoing.

A fifth aspect of the present invention is embodied by a contrast mediainjector system that includes a powerhead, a first console (e.g., aremote console), a CAN-compliant injector communication bus, and aninjection data management module. The powerhead includes a housing, amotorized drive ram, and a syringe mount (e.g., of any appropriate type,for instance, a faceplate). The motorized drive ram of the powerhead isdesigned to move along an axis, where at least part of the motorizeddrive ram is located within the housing. The syringe mount of thepowerhead is designed to at least substantially immobilize a barrel ofthe syringe relative to the housing of the powerhead such that the driveram can move a plunger of the syringe within and relative to the syringebarrel. The first console of the contrast media injector system is incommunication with the powerhead, includes a first display, and can beutilized by a user of the contrast media injector system to programinjection parameters (e.g., to define an injection protocol having oneor more phases, each phase including injection parameters such as anamount of fluid to be injected and an injection flow rate, as well aspossibly one or more injection delays (sometimes referred to as “holds”and/or “pauses”), each of which can be of finite or infinite duration).The injection data management module includes a first data conversionmodule. This first data conversion module is operatively interconnectedwith the CAN-compliant injector communication bus, and is configured toconvert CAN-compliant data from the CAN-compliant injector communicationbus to HL-7-compliant data (where “HL-7” is “Health Level 7”).

A number of feature refinements and additional features are applicableto the fifth aspect of the present invention. These feature refinementsand additional features may be used individually or in any combinationin relation to the fifth aspect. As such, each of the following featuresthat will be discussed may be, but are not required to be, used with anyother feature or combination of features of the fifth aspect. Thefollowing discussion is applicable to the fifth aspect, up to the startof the discussion of a sixth aspect of the present invention.

The CAN-compliant data from the CAN-compliant injector communication busmay be of any appropriate CAN version. The HL-7-compliant data may be ofany appropriate HL-7 or “Health Level 7” version (e.g., version 1.0,2.0, or 3.0).

CAN-compliant data from the CAN-compliant injector communication bus maybe acquired for conversion by the first data conversion module in anyappropriate manner. This acquired CAN-compliant data may be provideddirectly to the first data conversion module for conversion from aCAN-compliant format to an HL-7-compliant format. Another option is forthis acquired CAN-compliant data to be provided indirectly to the firstdata conversion module (e.g., through a second data conversion modulediscussed below) for conversion from a CAN-compliant format to anHL-7-compliant format.

The first data conversion module may convert CAN-compliant data from theCAN-compliant injector communication bus to HL-7-compliant data in anyappropriate manner. This conversion may be characterized as converting agiven data object within one standard to the appropriate data object andformat in another standard. The first data conversion module may beincorporated by the contrast media injector system in any appropriatemanner to provide the noted conversion function. For instance, the firstdata conversion module could be incorporated by an existing subsystem ofthe contrast media injector system, such as a powerhead, a remoteconsole, or a powerpack. Another option would be for the first dataconversion module to be a completely separate subsystem of the contrastmedia injector system. For instance, the first data conversion modulecould be separate from, but operatively interconnected with, anothersubsystem of the contrast media injector system such as a powerhead,remote console, or a powerpack.

The injection data management module may include a second dataconversion module that is operatively interconnected with theCAN-compliant injector communication bus. This second data conversionmodule may be configured to convert CAN-compliant data from theCAN-compliant injector communication bus from a first CAN-compliantformat (e.g., CAN 2.0A) to a second CAN-compliant format (e.g., CiA425). The first and second data conversion modules may be characterizedas being connected in parallel in one configuration. For instance, thefirst data conversion module may convert CAN-compliant data from thenoted first CAN-compliant format to HL-7-compliant data, and the seconddata conversion module may convert CAN-compliant data from the notedfirst CAN-compliant format to the second CAN-compliant format (e.g., a“parallel” stream or feed of the same CAN-compliant data from theCAN-compliant injector communication bus could be provided to each ofthe first data conversion module and the second data conversion module,including on a simultaneous basis).

The first and second data conversion modules may be characterized asbeing connected in series in another configuration. For instance, thefirst data conversion module may convert CAN-compliant data from thenoted second CAN-compliant format (e.g., CiA 425) to HL-7-compliantdata. That is, CAN-compliant data (in a first CAN-compliant format) fromthe CAN-compliant injector communication bus may be transmitted to thesecond data conversion module, which may then convert this CAN-compliantdata from the first CAN-compliant format (e.g., CAN 2.0A) to the secondCAN-compliant format (e.g., CiA 425). CAN-compliant data in the secondCAN-compliant format may then be transmitted to the first dataconversion module, which may then convert this CAN-compliant data fromthe second CAN-compliant format to the HL-7-compliant format. In such acase, the CAN-compliant injector communication bus may be characterizedas being indirectly interconnected with the first data conversion module(via the second data conversion module).

The injection data management module may include a third data conversionmodule that is operatively interconnected with the CAN-compliantinjector communication bus. This third data conversion module may beconfigured to convert CAN-compliant data from the CAN-compliant injectorcommunication bus from a first CAN-compliant format (e.g., CAN 2.0A) toa PACS-compliant format (e.g., DICOM). The first, second, and third dataconversion modules may be characterized as being connected in parallelin one configuration. For instance, the first data conversion module mayconvert CAN-compliant data from the noted first CAN-compliant format tothe HL-7-compliant format, the second data conversion module may convertCAN-compliant data from the noted first CAN-compliant format to thesecond CAN-compliant format, and the third data conversion module mayconvert CAN-compliant data from the noted first CAN-compliant format toa PACS-compliant format (e.g., a “parallel” stream or feed of the sameCAN-compliant data from the CAN-compliant injector communication buscould be provided to each of the first, second, and third dataconversion modules, including on a simultaneous basis).

The second and third data conversion modules may be characterized asbeing connected in series in another configuration (including where thefirst and third data conversion modules may be characterized as stillbeing connected in parallel). For instance, the third data conversionmodule may convert CAN-compliant data from the noted secondCAN-compliant format (e.g., CiA 425) to a PACS-compliant format. Thatis, CAN-compliant data (in a first CAN-compliant format) from theCAN-compliant injector communication bus may be transmitted to thesecond data conversion module, which may then convert this CAN-compliantdata from the first CAN-compliant format (e.g., CAN 2.0A) to the secondCAN-compliant format (e.g., CiA 425). CAN-compliant data in the secondCAN-compliant format may then be transmitted to the third dataconversion module, which may then convert this CAN-compliant data fromthe second CAN-compliant format to a PACS-compliant format. In such acase, the CAN-compliant injector communication bus may be characterizedas being indirectly interconnected with the third data conversion module(via the second data conversion module).

A medical system may utilize an imaging system and a medical informationsystem, and the injection data management module may be configured toinclude the above-noted second data conversion module. The first dataconversion module may be operatively interconnected with the medicalinformation system (e.g., to provide injection-related or contrastadministration data from the contrast media injector system to themedical information system in an HL-7-compliant format). The second dataconversion module may be operatively interconnected with the imagingsystem (e.g., to provide injection-related or contrast administrationdata from the contrast media injection system to the imaging system, forinstance by converting the injection-related or contrast administrationdata from one CAN-compliant format (e.g., CAN 2.0A) to anotherCAN-compliant format (e.g., CiA 425)).

The injection data management module may include first and secondcommunication ports. The first communication port may be used to provideconverted data from the CAN-compliant injector communication bus to amedical information system operatively interconnected with the injectiondata management module (e.g., converted data may be output from thefirst data conversion module through a first communication port;converted data may be output from the second data conversion module tothe first data conversion module through one first communication port,and converted data may be output from the first data conversion modulethrough another first communication port). The second communication portmay be used to provide converted data from the CAN-compliant injectorcommunication bus to an imaging system operatively interconnected withthe injection data management module.

The contrast media injector system may include a first housing (e.g., apowerpack). The above-noted second data conversion module may bedisposed within this first housing, and there may be a communicationlink (e.g., a wired communication link, such as an appropriatecommunication cable) between the first housing and a powerhead of thecontrast media injector system. In a first configuration, the first andsecond data conversion modules are each disposed within the noted firsthousing (e.g., within the powerpack). The first housing in thisconfiguration may include first and second communication ports of anyappropriate type (e.g., on an output side of this first housing), wherethe first communication port is operatively interconnected with thefirst data conversion module, and where the second communication port isoperatively interconnected with the second data conversion module (e.g.,converted data may be transmitted from the first data conversion modulethrough the first communication port; converted data may be transmittedfrom the second data conversion module through the second communicationport). In the case where a contrast media injector system of this firstconfiguration is utilized by the above-noted medical system, the firstdata conversion module may be operatively interconnected with themedical information system through the first communication port of thisfirst housing, while the second data conversion module may beoperatively interconnected with the imaging system through the secondcommunication port of this first housing.

In another configuration, the first data conversion module is notlocated within the noted first housing (e.g., a powerpack), but whichmay still contain the second data conversion module. The first dataconversion module may be a completely separate unit from the firsthousing. The first housing in this configuration may still utilize firstand second communication ports of any appropriate type (e.g., on anoutput side of the first housing), where each of the first and secondcommunication ports are operatively interconnected with the second dataconversion module (e.g., converted data may be transmitted from thesecond data conversion module through each of the first and secondcommunication ports). There may be a communication link of anyappropriate type between the first communication port (e.g., on anoutput side of the first housing) and the first data conversion module(e.g., a wired communication link, such as an appropriate communicationcable). That is, the second data conversion module may be operativelyinterconnected with the first data conversion module through the firstcommunication port. In the case where an injection data managementmodule of this second configuration is utilized by a medical system, thefirst data conversion module may be operatively interconnected with themedical information system through the first communication port of thesecond data conversion module (as the second data conversion module isable to transmit converted data to the first data conversion modulethrough the first communication port, and the first data conversionmodule is then able to further convert this data for provision to amedical information system or the like), while the second dataconversion module may be operatively interconnected with the imagingsystem through the second communication port of the second dataconversion module.

The first and second communication ports of the first housing in theabove-noted second configuration may each receive CAN-compliant datafrom the second data conversion module in a common CAN-compliant format(e.g., CiA 425). That is, CAN-compliant data that has been converted bythe second data conversion module may be transmitted to an imagingsystem through the second communication port of the second dataconversion module, and also to the first data conversion module throughthe first communication port of the second data conversion module. Thefirst data conversion module would then convert this CAN-compliant datato HL-7-compliant data (e.g., for subsequent provision to a medicalinformation system through a first communication port of the first dataconversion module).

The injection data management module may be characterized as includingfirst and second communication nodes. In a first embodiment: 1) thefirst communication node is operatively interconnected with theCAN-compliant injector communication bus (e.g., directly or indirectlythrough the above-discussed second data conversion module); 2) onlyone-way communication is allowed between the CAN-compliant injectorcommunication bus and the second communication node through the firstcommunication node (e.g., CAN-compliant data may be transmitted from theCAN-compliant injector communication bus to the first data conversionmodule and then ultimately to a medical information system, butdata/commands from the medical information system may not be sentthrough the first data conversion module to the CAN-compliant injectorcommunication bus through the first communication node); and 3) theinjection data management module accommodates two-way communicationthrough the second communication node. In a second embodiment: 1) thefirst communication node is operatively interconnected with theCAN-compliant injector communication bus (e.g. directly or indirectlythrough the above-discussed second data conversion module); and 2) theinjection data management module is of a pull-type data transferconfiguration in relation to the second communication node. In a thirdembodiment: 1) the first communication node is operativelyinterconnected with the CAN-compliant injector communication bus (e.g.directly or indirectly through the above-discussed second dataconversion module); and 2) the injection data management module isconfigured to output data to the second communication node only inresponse to a data request received by the injection data managementmodule through the second communication node. In each of these threeembodiments, injection-related or contrast administration data may besent to the first data conversion module through the first communicationnode, the injection data management module may receive a request forinjection-related or contrast administration data through the secondcommunication node (e.g., from a hospital information system), and dataconverted by the first data conversion module may be made availablethrough the second communication node (e.g., for provision to a hospitalinformation system).

Another embodiment has the injection data management module beingconfigured such that: 1) the first communication node is operativelyinterconnected with the CAN-compliant injector communication bus (e.g.,directly or indirectly through the above-discussed second dataconversion module); and 2) the second communication node is operativelyinterconnected with a medical information system of any appropriate type(e.g., a hospital information system; an electronic medical recordssystem). The injection data management module may be characterized inthis case as being of a push-type configuration—the first dataconversion module may be configured to and/or allow data to betransmitted to the medical information system without first receiving arequest for data from the medical information system. Anothercharacterization is that the injection data management module may beconfigured to transmit data (previously converted by the first dataconversion module) to the medical information system on an automated orprogrammed basis. In each of these instances, injection-related orcontrast administration data may be sent to the first data conversionmodule through the first communication node, the first data conversionmodule may then translate this data into an HL-7-compliant format, andthe HL-7-compliant data may then ultimately be transmitted from theinjection data management module to the medical information systemthrough the second communication node.

The injection data management module may also be of a push/pullconfiguration. The injection data management module may be configured toaccommodate transmission of data to a medical information system inresponse to receiving a request for data (e.g., a pull-type datatransmission). The injection data management module may also beconfigured to transmit data to a medical information system on anautomated or programmed basis (e.g., a push-type data transmission).

A sixth aspect of the present invention is embodied by a medical systemthat includes a contrast media injector system, an imaging system, afirst console, a contrast media storage/dispensing unit, a medicalinformation system, and an injection data management module. Thecontrast media injector system and imaging system are operativelyinterconnected. The first console is operatively interconnected with atleast one of the contrast media injector system and the imaging system,and includes both a first display and a first user input device. Thecontrast media storage/dispensing unit includes a plurality of contrastmedia containers having contrast media therein, and each such contrastmedia container incorporates a data storage device (e.g., RF data tag; abar code). In this regard, the contrast media injector system includes areader that is operable to at least read data from a data storage deviceof a contrast media container having contrast media to be used by thecontrast media injector system. The injection data management moduleincludes a first data conversion module. The injection data managementmodule is disposed between the medical information system and aninjector communication bus of the contrast media injector system, and isoperatively interconnected with each of the medical information systemand injector communication bus.

A seventh aspect of the present invention is embodied by a medicalsystem that includes a contrast media injector system, an imagingsystem, a first console, a contrast media storage/dispensing unit, atleast one renal function assessment module, a medical informationsystem, and an injection data management module. The contrast mediainjector system and imaging system are operatively interconnected. Thefirst console is operatively interconnected with at least one of thecontrast media injector system and imaging system, and includes both afirst display and a first user input device. The contrast mediastorage/dispensing unit includes a plurality of contrast mediacontainers having contrast media therein. The injection data managementmodule includes a first data conversion module. The injection datamanagement module is disposed between the medical information system andan injector communication bus of the contrast media injector system, andis operatively interconnected with each of the medical informationsystem and injector communication bus.

A number of feature refinements and additional features are separatelyapplicable to each of above-noted sixth and seventh aspects of thepresent invention. These feature refinements and additional features maybe used individually or in any combination in relation to each of theabove-noted sixth and seventh aspects of the present invention. As such,each of the following features that will be discussed may be, but arenot required to be, used with any other feature or combination offeatures of each of the sixth and seventh aspects.

One or more data readers may be utilized by the contrast media injectorsystem, and may be incorporated by the contrast media injector system inany appropriate manner (e.g., in a syringe mount; as a separate unit(e.g., a wand) that is detachably connected with another portion of thecontrast media injector system). Such a data reader may be used to readdata from a data storage device of any appropriate type (e.g., a datatag on a syringe or other contrast media container; a bar code on apatient wristband; a data tag on the badge of medical personnel). Thedata reader may be in the form of an electromagnetic device, such as anRFID reader.

The first data conversion module may be incorporated by the medicalsystem in any appropriate manner. The first data conversion module couldbe incorporated by the contrast media injector system in any appropriatemanner, for instance in accordance with the above-noted fifth aspect.However, the first data conversion module could be incorporated by themedical system so as to be physically separate from each of the contrastmedia injector system and the medical information system. The first dataconversion module may be configured to communicate on at least a one-waybasis (via the operative connection) with each of the injectorcommunication bus and the medical information system.

The first data conversion module may be configured to convert data froma first format (e.g., one format) to a second format (e.g., a differentformat). For instance, the first data conversion module may receive datain a first format (e.g., directly or indirectly from the injectorcommunication bus), and data transmitted from the first data conversionmodule may be in a second format (e.g., for receipt by the medicalinformation system). In one embodiment, the first format isCAN-compliant (e.g., CAN 2.0A; CiA 425), and the second format isHL-7-compliant. In this regard, each of the sixth and seventh aspects ofthe present invention may incorporate the combination of featuresrequired by the fifth aspect of the present invention, as well as any ofthe refinements and additional features discussed above in relation tothe fifth aspect.

The injection data management module may include a single dataconversion module (e.g., a first data conversion module). Multiple dataconversion modules may be utilized by the injection data managementmodule (e.g., a first data conversion module, along with at least one ofa second data conversion module and a third data conversion module). Agiven data conversion module of the injection data management module mayconvert data from the contrast media injector system into a differentformat, for instance into a HL-7-compliant format or into aPACS-compliant format (e.g., DICOM). Data from the contrast mediainjector system may be in the form of CAN-compliant data. A given dataconversion module of the injection data management module may convertdata from the contrast media injector system from one CAN-compliantformat into a different CAN-compliant format (e.g., for provision to theimaging system). A given data conversion module of the injection datamanagement module may convert data, received from the contrast mediainjector system, from a CAN-compliant format into an HL-7-compliantformat or a PACS-compliant format (e.g., DICOM). In the case wheremultiple data conversion modules are utilized by the injection datamanagement module, each data conversion module may convert data into adifferent format (e.g., one data conversion module may convert data intoan HL-7-compliant format, and another data conversion module may convertdata into a PACS-compliant format such as DICOM). In one embodiment, thefirst data conversion module converts data from a CAN-compliant formatto a non-CAN-compliant format (e.g., HL-7 or DICOM).

The medical system may include at least one patient renal functionassessment module. Such a renal function assessment module may beconfigured to provide at least one patient renal function check at leastat some point in time prior to injecting contrast media into a patient(or administering contrast media to a patient) using the contrast mediainjector system, where this contrast media may have been provided ordispensed by a contrast media storage/dispensing unit. In oneembodiment, a renal function assessment module is incorporated by thecontrast media injector system (e.g., a first renal function assessmentmodule). This first renal function assessment module may be configuredto provide at least one patient renal function check prior to thecontrast media injector system being operated to inject contrast mediainto a patient (or administer contrast media to a patient). As such, thefirst aspect of the present invention may be utilized by each of thesixth and seventh aspects.

In one embodiment, a renal function assessment module is incorporated bya contrast media storage/dispensing unit (e.g., a second renal functionassessment module). This second renal function assessment module may beconfigured to provide at least one patient renal function check prior toreleasing any contrast media container from the contrast mediastorage/dispensing unit (e.g., for use by the contrast media injectorsystem). As such, the third aspect of the present invention may beutilized by each of the sixth and seventh aspects.

The medical system may include at least one data store. This data storemay store a plurality of contrast media types and a correspondingthreshold renal function for each contrast media type. As such, thesecond aspect of the present invention may be utilized by each of thesixth and seventh aspects.

A number of feature refinements and additional features are separatelyapplicable to each of above-noted fifth, sixth, and seventh aspects ofthe present invention. These feature refinements and additional featuresmay be used individually or in any combination in relation to each ofthe above-noted fifth, sixth, and seventh aspects of the presentinvention. As such, each of the following features that will bediscussed may be, but are not required to be, used with any otherfeature or combination of features of the each of the fifth, sixth, andseventh aspects.

Any medical information system described in relation to the fifth,sixth, and seventh aspects may be of any appropriate type and/orconfiguration. For instance, such a medical information system could bein the form of a hospital or healthcare information system (HIS), aradiological information system (RIS), a pharmacy information system(PIS), a hospital management system (HMS), or the like. Each suchmedical information system may include one more computers, one or moreuser/data input devices, one or more data storage devices or systems,and the like, and may be arranged and/or distributed in any appropriatemanner (e.g., using one or more networks of any appropriate type, suchas a local area network, the Internet, a wide area network, or anycombination thereof).

Any medical system that utilizes any one or more of the above-notedfifth, sixth, and seventh aspects of the present invention may utilize adata structure having a plurality of data fields. For instance, amedical information system may utilize such a data structure.Representative data fields for this data structure include one or morefields directed to one or more of the following: 1) patient information;2) physician information; 3) imaging procedure information; 4)prescribed contrast media information (e.g., information on contrastmedia that has been prescribed for injection or administration to apatient); 5) dispensed contrast media information (e.g., information oncontrast media that has been provided or dispensed by the contrast mediastorage/dispensing unit for subsequent use by the contrast mediainjector system); and 6) administered contrast media information (e.g.,information on contrast media that has been injected or administered bythe contrast media injector system). Data in each of these fields may belinked in any appropriate manner to define a data record for this datastructure (e.g., a data record having data for one or more of theabove-noted data fields).

Prescribed contrast media data (e.g., the contrast media volume that hasbeen prescribed for injection into a patient; the concentration of thecontrast media that has been prescribed for injection into a patient;the flow rate(s) that has been prescribed for the injection of contrastmedia into a patient), dispensed contrast media data (e.g., the contrastmedia volume that has been dispensed from the contrast mediastorage/dispensing unit for subsequent injection into a patient; theconcentration of the contrast media that has been dispensed from thecontrast media storage/dispensing for subsequent injection into apatient), and administered contrast media data (e.g., the contrast mediavolume that was actually injected into or administered to a patient bythe contrast media injector system; the concentration of the contrastmedia that was actually injected into or administered to a patient bythe contrast media injector system; the flow rate(s) that was actuallyinjected into or administered to a patient by the contrast mediainjector system) may be stored in a data structure of the medicalsystem. Additional data on the contrast media that has been prescribed,dispensed, and/or administered may be stored in the data structure ofthe medical system, including without limitation the brand name of thecontrast media, the manufacturer of the contrast media, the lot numberof the contrast media, the expiration date of the contrast media, andthe manufacture date for the contrast media. The prescribed contrastmedia data, dispensed contrast media data, and administered contrastmedia data described herein may be characterized as injection-related orcontrast administration data for purposes of the present invention. Theprescribed contrast media data, dispensed contrast media data, andadministered contrast media data each may be used for any appropriatepurpose. For instance, prescribed contrast media data, dispensedcontrast media data, and/or administered contrast media data may beutilized by electronic medical records, inventory tracking systems,medical billing systems, imaging, pharmacy, laboratory, or radiologysystems, or the like.

The injection data management module may utilize at least one dataconversion module (e.g., the described first data conversion module).Such an injection data management module may or may not include at leastone of a second data conversion module and a third data conversionmodule as described herein. One or more data conversion modules of theinjection data management module could be disposed in a common housingor in a single unit. One or more data conversion modules of theinjection data management module could be disposed in a common housingor in a single unit, one or more data conversion modules of theinjection data management module could each be disposed in a separatehousing or unit, or both.

The injection data management module may utilize a data processingmodule or unit. The data processing module could be disposed in a commonunit with one or more data conversion modules used by the injection datamanagement module. The data processing module could also be disposed ina separate unit in relation to each data conversion module used by theinjection data management module.

One or more processors may be used by the injection data managementmodule (e.g., its data processing module) to process requests forcontrast administration data received by the injection data managementmodule from one or more medical information systems (e.g., HIS, RIS, anelectronic medical records system), to facilitate transmission of datafrom the injection data management module to one or more medicalsystems, to store information on the injection data management module,or for any other functionality provided by the injection data managementmodule.

The injection data management module may include an appropriate datastorage system of any appropriate type or types and of any appropriatearchitecture (e.g., memory of any appropriate type or types; one or moredata storage devices). The injection data management module may use apush-type data transmission configuration, a pull-type data transmissionconfiguration, or a push/pull-type data transmission configuration(e.g., in relation to the first data conversion module, in relation toany second data conversion module, and/or in relation to any third dataconversion module). In one embodiment, the data processing module andthe data storage system are disposed in a common unit. Converted datafrom each data conversion module may be transmitted to the data storagesystem (whether a given data conversion module is contained within thesame unit as the data processing module and data storage system, orwhether a given data conversion module is in a physically separate unitform the data processing module and data storage system). One or moremedical information systems may communicate with the data processingmodule, including in relation to the transmission of data from the datastorage system of the injection data management module to one or moremedical information systems.

A user interface (e.g., at least one user input device of anyappropriate type, a display, or both) may be operatively interconnectedwith the injection data management module. Such a user interface may beused to communicate with the data processing module, the data storagesystem, each data conversion module, or any combination thereof. Theinjection data management module may utilize software for use inconverting data from one format to another, storing data on theinjection data management module, transmitting data from the injectiondata management module, processing requests for data, and/orcommunicating with one or more medical systems (e.g., a medicalinformation system). The injection data management module may includeone or more communication ports of any appropriate type, including atleast one communication port to allow software updates to be downloadedto/installed on the injection data management module (e.g., an Ethernetport for allowing software updates to be downloaded to the injectiondata management module from the Internet). The injection data managementmodule could use a separate communication port to communicate with eachmedical information system of sub-system of a medical system. Theinjection data management module could have a separate communicationport for each data format stored on its data storage system (e.g., aseparate communication port for HL-7-compliant data; a separatecommunication port for PACS-compliant-data; a separate communicationport for CAN-compliant data, for instance for communications with animaging system).

The contrast media injector system may be used in conjunction with animaging system. Such an imaging system (e.g., a scanner and a remoteconsole) may use any appropriate imaging technology (e.g., computedtomography or CT imaging; magnetic resonance imaging or MRI; singlephoton emission computed tomography or SPECT imaging; positron emissiontomography or PET imaging; X-ray imaging; angiographic imaging; opticalimaging; ultrasound imaging).

The contrast media injector system may utilize a first console (e.g., aremote console). The first console may be of any appropriate type (e.g.,a desktop computer; a laptop computer), and may include one or moredisplays or monitors, one or more processors, one or more data or userinput devices of any appropriate type (e.g., keyboard, mouse, touchscreen, joystick, trackball), memory of any appropriatetype/configuration, one or more data storage devices of any appropriatetype (e.g., a hard drive, flash drive), or any combination thereof. Thefirst console may be located in a different room (e.g., a control room)than a powerhead of the contrast media injector system (e.g., in animaging room), although the first console could be located in the sameroom as such a powerhead (e.g., in an imaging room). The first consolemay be operatively interconnected with only the powerhead, or the remoteconsole could be operatively interconnected with both the powerhead andan imaging system. The first console in this case could be a sharedconsole for the contrast media injector system and the imaging system,the first console could actually be the console for the contrast mediainjector system (but configured to communicate with and/or control atleast certain aspects of the imaging system), or the first console couldactually be the console for the imaging system (but configured tocommunicate with and/or control at least certain aspects of the contrastmedia injector system).

A number of feature refinements and additional features are separatelyapplicable to each of above-noted first, second, third, fourth, fifth,sixth, and seventh aspects of the present invention. These featurerefinements and additional features may be used individually or in anycombination in relation to each of the above-noted aspects. Any featureof any other various aspects of the present invention that is intendedto be limited to a “singular” context or the like will be clearly setforth herein by terms such as “only,” “single,” “limited to,” or thelike. Merely introducing a feature in accordance with commonly acceptedantecedent basis practice does not limit the corresponding feature tothe singular (e.g., indicating that a power injector includes “asyringe” alone does not mean that the power injector includes only asingle syringe). Moreover, any failure to use phrases such as “at leastone” also does not limit the corresponding feature to the singular(e.g., indicating that a power injector includes “a syringe” alone doesnot mean that the power injector includes only a single syringe). Use ofthe phrase “at least generally” or the like in relation to a particularfeature encompasses the corresponding characteristic and insubstantialvariations thereof (e.g., indicating that a syringe barrel is at leastgenerally cylindrical encompasses the syringe barrel being cylindrical).Finally, a reference of a feature in conjunction with the phrase “in oneembodiment” does not limit the use of the feature to a singleembodiment.

Any module, protocol, logic, or the like that may be utilized by any ofthe various aspects of the present invention may be implemented in anyappropriate manner, including without limitation in any appropriatesoftware, firmware, or hardware, using one or more platforms, using oneor more processors, using memory of any appropriate type, using anysingle computer of any appropriate type or a multiple computers of anyappropriate type and interconnected in any appropriate manner, or anycombination thereof. Any such module, protocol, logic, or the like maybe implemented at any single location or at multiple locations that areinterconnected in any appropriate manner (e.g., via any type of networkor combination of networks).

Any power injector that may be utilized to provide a fluid discharge maybe of any appropriate size, shape, configuration, and/or type. Any suchpower injector may utilize one or more syringe plunger drivers of anyappropriate size, shape, configuration, and/or type, where each suchsyringe plunger driver is capable of at least bi-directional movement(e.g., a movement in a first direction for discharging fluid; a movementin a second direction for accommodating a loading and/or drawing offluid and/or so as to return to a position for a subsequent fluiddischarge operation), and where each such syringe plunger driver mayinteract with its corresponding syringe plunger in any appropriatemanner (e.g., by mechanical contact; by an appropriate coupling(mechanical or otherwise)) so as to be able to advance the syringeplunger in at least one direction (e.g., to discharge fluid). Eachsyringe plunger driver may utilize one or more drive sources of anyappropriate size, shape, configuration, and/or type. Multiple drivesource outputs may be combined in any appropriate manner to advance asingle syringe plunger at a given time. One or more drive sources may bededicated to a single syringe plunger driver, one or more drive sourcesmay be associated with multiple syringe plunger drivers (e.g.,incorporating a transmission of sorts to change the output from onesyringe plunger to another syringe plunger), or a combination thereof.Representative drive source forms include a brushed or brushlesselectric motor, a hydraulic motor, a pneumatic motor, a piezoelectricmotor, or a stepper motor.

Any such power injector may be used for any appropriate applicationwhere the delivery of one or more medical fluids is desired, includingwithout limitation any appropriate medical imaging application (e.g.,computed tomography or CT imaging; magnetic resonance imaging or MRI;single photon emission computed tomography or SPECT imaging; positronemission tomography or PET imaging; X-ray imaging; angiographic imaging;optical imaging; ultrasound imaging) and/or any appropriate medicaldiagnostic and/or therapeutic application (e.g., injection ofchemotherapy, pain management, etc.). Any such power injector may beused in conjunction with any component or combination of components,such as an appropriate imaging system (e.g., a CT or MR scanner). Forinstance, information could be conveyed between any such power injectorand one or more other components (e.g., scan delay information,injection start signal, injection rate).

Any appropriate number of syringes may be utilized with any such powerinjector in any appropriate manner (e.g., detachably; front-loaded;rear-loaded; side-loaded), any appropriate medical fluid may bedischarged from a given syringe of any such power injector (e.g.,contrast media, therapeutic fluid, a radiopharmaceutical, saline, andany combination thereof), and any appropriate fluid may be dischargedfrom a multiple syringe power injector configuration in any appropriatemanner (e.g., sequentially, simultaneously), or any combination thereof.In one embodiment, fluid discharged from a syringe by operation of thepower injector is directed into a conduit (e.g., medical tubing set),where this conduit is fluidly interconnected with the syringe in anyappropriate manner and directs fluid to a desired location (e.g., to acatheter that is inserted into a patient for injection). Multiplesyringes may discharge into a common conduit (e.g., for provision to asingle injection site), or one syringe may discharge into one conduit(e.g., for provision to one injection site), while another syringe maydischarge into a different conduit (e.g., for provision to a differentinjection site). In one embodiment, each syringe includes a syringebarrel and a plunger that is disposed within and movable relative to thesyringe barrel. This plunger may interface with the power injector'ssyringe plunger drive assembly such that the syringe plunger driveassembly is able to advance the plunger in at least one direction, andpossibly in two different, opposite directions.

As used herein, the term “detachably interconnected” describes arelationship between components where the components are interconnectedyet retain the ability to be detached from each other where, afterdetaching, each of the components remains in a usable condition. Forexample, “a power injector syringe being detachably interconnected witha powerhead” describes a condition where the power injector syringe iscurrently interconnected to the powerhead in a manner that allows forthe power injector syringe to be detached from the powerhead.Furthermore, after such detaching, both the power injector syringe andthe powerhead retain the ability to be interconnected (e.g., detachably)with each other (or another component).

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A is a schematic of one embodiment of a power injector.

FIG. 1B is a perspective view of one embodiment of a portablestand-mounted, dual-head power injector.

FIG. 1C is an enlarged, partially exploded, perspective view of apowerhead used by the power injector of FIG. 1B.

FIG. 1D is a schematic of one embodiment of a syringe plunger driveassembly used by the power injector of FIG. 1B.

FIG. 2A is a perspective view of an injector head of an injector, havinga syringe attached to a forward area thereof.

FIG. 2B is a perspective view of one exemplary embodiment of a syringemount in an assembled condition.

FIG. 2C is an exploded view of the syringe mount of FIG. 2B.

FIG. 3A is a cutaway view of the syringe mount of FIGS. 2B and 2C,particularly showing an actuator of the syringe mount.

FIG. 3B is a cross-sectional view, taken along line 3B-3B of FIG. 3A.

FIG. 4A is a cutaway view of syringe mount of FIGS. 2B and 2C,particularly showing first and second movable members of the syringemount in an open position.

FIG. 4B is a cross-sectional view, taken along line 4B-4B of FIG. 4A,and shows a coupling mechanism of a syringe plunger positioned inproximity to a plunger coupling element of a drive ram.

FIG. 5A is a cutaway view of the syringe mount of FIGS. 2B and 2C,particularly showing the first and second movable members in a closedposition and engaging a syringe.

FIG. 5B is a cross-sectional view, taken along line 5B-5B of FIG. 5A,and shows the coupling mechanism on the backside of the syringe plungerengaged with the plunger coupling element of the drive ram.

FIG. 6 is a perspective schematic of one embodiment of a power injectorsyringe clamp assembly that may be used by a power injector syringemount (e.g., FIGS. 2B and 2C), along with a proximal portion of arepresentative power injector syringe.

FIG. 7 is a plan view of one RFID antenna layout that may be utilized bythe power injector syringe clamp assembly of FIG. 6 (end surfaces beingillustrated).

FIG. 8A is a plan view of another RFID antenna layout that may beutilized by the power injector syringe clamp assembly of FIG. 6(interior surface being illustrated).

FIG. 8B is a plan view of another RFID antenna layout that may beutilized by the power injector syringe clamp assembly of FIG. 6(interior surface being illustrated).

FIG. 9 is a schematic of an option for providing power to an RFIDantenna of a power injector syringe clamp assembly, using a pivot pin.

FIG. 10 is a schematic view of another RFID antenna layout that may beutilized by the power injector syringe clamp assembly of FIG. 6, alongwith another option for providing power to an RFID antenna.

FIG. 11 is a schematic of one embodiment of an imaging suite thatincorporates patient renal function assessment functionality.

FIG. 12 is a schematic of one embodiment of a control module thatincorporates renal function assessment functionality and that may beused by one or more components of the imaging suite of FIG. 11.

FIG. 13 is a schematic of one embodiment of a protocol that may be usedby a renal function assessment module of the control module of FIG. 12.

FIG. 14 is a schematic of another embodiment of a protocol that may beused by the renal function assessment module of the control module ofFIG. 12.

FIG. 15 is a schematic of one embodiment of a contrast mediastorage/dispensing unit that incorporates renal function assessmentfunctionality.

FIG. 16 is one embodiment of a protocol that may be used by the contrastmedia storage/dispensing unit of FIG. 15 for purposes of determiningwhether a contrast media container should be released from the unit.

FIG. 17 is another embodiment of a protocol that may be used by thecontrast media storage/dispensing unit of FIG. 15 for purposes ofdetermining whether a contrast media container should be released fromthe unit.

FIG. 18A is one embodiment of a medical system having an injection datamanagement module with contrast media injection/administration dataformat conversion capabilities.

FIG. 18B is a schematic of a representative embodiment for the injectiondata management module used by the medical system of FIG. 18A.

FIG. 19 is a functional schematic of an embodiment of the injection datamanagement module used by the medical system of FIG. 18A.

FIG. 20 is a functional schematic of an embodiment of the injection datamanagement module used by the medical system of FIG. 18A.

FIG. 21 is one embodiment of a data management protocol for theinjection data management module configuration of FIG. 19.

FIG. 22 is one embodiment of a data management protocol for theinjection data management module configuration of FIG. 20.

FIG. 23A-D is one embodiment of a data structure that may be used by themedical system of FIG. 18A.

FIG. 24 is one embodiment of an imaging protocol that may be executed bythe medical system of FIG. 18A.

DETAILED DESCRIPTION

FIG. 1A presents a schematic of one embodiment of a power injector 210having a powerhead 212. One or more graphical user interfaces or GUIs211 may be associated with the powerhead 212. Each GUI 211: 1) may be ofany appropriate size, shape, configuration, and/or type; 2) may beoperatively interconnected with the powerhead 212 in any appropriatemanner; 3) may be disposed at any appropriate location; 4) may beconfigured to provide one or any combination of the following functions:controlling one or more aspects of the operation of the power injector210; inputting/editing one or more parameters associated with theoperation of the power injector 210; and displaying appropriateinformation (e.g., associated with the operation of the power injector210); or 5) any combination of the foregoing. Any appropriate number ofGUIs 211 may be utilized. In one embodiment, the power injector 210includes a GUI 211 that is incorporated by a console that is separatefrom but which communicates with the powerhead 212. In anotherembodiment, the power injector 210 includes a GUI 211 that is part ofthe powerhead 212. In yet another embodiment, the power injector 210utilizes one GUI 211 on a separate console that communicates with thepowerhead 212, and also utilizes another GUI 211 that is on thepowerhead 212. Each GUI 211 could provide the same functionality or setof functionalities, or the GUIs 211 may differ in at least some respectin relation to their respective functionalities.

A syringe 228 may be installed on this powerhead 212 and, wheninstalled, may be considered to be part of the power injector 210. Someinjection procedures may result in a relatively high pressure beinggenerated within the syringe 228. In this regard, it may be desirable todispose the syringe 228 within a pressure jacket 226. The pressurejacket 226 is typically associated with the powerhead 212 in a mannerthat allows the syringe 228 to be disposed therein as a part of or afterinstalling the syringe 228 on the powerhead 212. The same pressurejacket 226 will typically remain associated with the powerhead 212, asvarious syringes 228 are positioned within and removed from the pressurejacket 226 for multiple injection procedures. The power injector 210 mayeliminate the pressure jacket 226 if the power injector 210 isconfigured/utilized for low-pressure injections and/or if the syringe(s)228 to be utilized with the power injector 210 is (are) of sufficientdurability to withstand high-pressure injections without the additionalsupport provided by a pressure jacket 226. Fluid discharged from thesyringe 228 may be directed into a conduit 238 of any appropriate size,shape, configuration, and/or type, which may be fluidly interconnectedwith the syringe 228 in any appropriate manner, and which may directfluid to any appropriate location (e.g., to a patient).

The powerhead 212 includes a syringe plunger drive assembly or syringeplunger driver 214 that interacts (e.g., interfaces) with the syringe228 (e.g., a plunger 232 thereof) to discharge fluid from the syringe228. This syringe plunger drive assembly 214 includes a drive source 216(e.g., a motor of any appropriate size, shape, configuration, and/ortype, optional gearing, and the like) that powers a drive output 218(e.g., a rotatable drive screw). A ram 220 may be advanced along anappropriate path (e.g., axial) by the drive output 218. The ram 220 mayinclude a coupler 222 for interacting or interfacing with acorresponding portion of the syringe 228 in a manner that will bediscussed below.

The syringe 228 includes a plunger or piston 232 that is movablydisposed within a syringe barrel 230 (e.g., for axial reciprocationalong an axis coinciding with the double-headed arrow B). The plunger232 may include a coupler 234. This syringe plunger coupler 234 mayinteract or interface with the ram coupler 222 to allow the syringeplunger drive assembly 214 to retract the syringe plunger 232 within thesyringe barrel 230. The syringe plunger coupler 234 may be in the formof a shaft 236 a that extends from a body of the syringe plunger 232,together with a head or button 236 b. However, the syringe plungercoupler 234 may be of any appropriate size, shape, configuration, and/ortype.

Generally, the syringe plunger drive assembly 214 of the power injector210 may interact with the syringe plunger 232 of the syringe 228 in anyappropriate manner (e.g., by mechanical contact; by an appropriatecoupling (mechanical or otherwise)) so as to be able to move or advancethe syringe plunger 232 (relative to the syringe barrel 230) in at leastone direction (e.g., to discharge fluid from the corresponding syringe228). That is, although the syringe plunger drive assembly 214 may becapable of bi-directional motion (e.g., via operation of the same drivesource 216), the power injector 210 may be configured such that theoperation of the syringe plunger drive assembly 214 actually only moveseach syringe plunger 232 being used by the power injector 210 in onlyone direction. However, the syringe plunger drive assembly 214 may beconfigured to interact with each syringe plunger 232 being used by thepower injector 210 so as to be able to move each such syringe plunger232 in each of two different directions (e.g. in different directionsalong a common axial path).

Retraction of the syringe plunger 232 may be utilized to accommodate aloading of fluid into the syringe barrel 230 for a subsequent injectionor discharge, may be utilized to actually draw fluid into the syringebarrel 230 for a subsequent injection or discharge, or for any otherappropriate purpose. Certain configurations may not require that thesyringe plunger drive assembly 214 be able to retract the syringeplunger 232, in which case the ram coupler 220 and syringe plungercoupler 234 may not be desired. In this case, the syringe plunger driveassembly 214 may be retracted for purposes of executing another fluiddelivery operation (e.g., after another pre-filled syringe 228 has beeninstalled). Even when a ram coupler 222 and syringe plunger coupler 232are utilized, it may be that these components may or may not be coupledwhen the ram 220 advances the syringe plunger 232 to discharge fluidfrom the syringe 228 (e.g., the ram 220 may simply “push on” the syringeplunger 234). Any single motion or combination of motions in anyappropriate dimension or combination of dimensions may be utilized todispose the ram coupler 222 and syringe plunger coupler 234 in a coupledstate or condition, to dispose the ram coupler 222 and syringe plungercoupler 234 in an un-coupled state or condition, or both.

The syringe 228 may be installed on the powerhead 212 using a syringemount of any appropriate configuration. For instance, the syringe 228could be configured to be installed directly on the powerhead 212. Asyringe mount may be characterized as a structure that allows a syringeto be installed on the powerhead 212 (e.g., via a detachable connectionwhere a syringe may be attached to and removed from the powerhead 212without damaging either the syringe or the powerhead 212). Generally,such a syringe mount may be further characterized as at leastsubstantially immobilizing the body or barrel 230 of the syringe 228such that the drive ram 220 of the injector 210 can move the syringeplunger 232 within and relative to the syringe barrel 230.

In the illustrated embodiment of FIG. 1A, a housing 224 (syringe mount)is appropriately mounted on the powerhead 212 to provide an interfacebetween the syringe 228 and the powerhead 212. This housing 224 may bein the form of an adapter to which one or more configurations ofsyringes 228 may be installed, and where at least one configuration fora syringe 228 could be installed directly on the powerhead 212 withoutusing any such adapter. The housing 224 may be in the form of afaceplate to which one or more configurations of syringes 228 may beinstalled. In this case, it may be such that a faceplate is required toinstall a syringe 228 on the powerhead 212—the syringe 228 could not beinstalled on the powerhead 212 without the faceplate. When a pressurejacket 226 is being used, it may be installed on the powerhead 212 inthe various manners discussed herein in relation to the syringe 228, andthe syringe 228 will typically thereafter be installed in the pressurejacket 226.

The housing 224 may be mounted on and remain in a fixed positionrelative to the powerhead 212 when installing a syringe 228. Anotheroption is to movably interconnect the housing 224 and the powerhead 212to accommodate installing a syringe 228. For instance, the housing 224may move within a plane that contains the double-headed arrow A toprovide one or more of a coupled state or condition and an un-coupledstate or condition between the ram coupler 222 and the syringe plungercoupler 234.

One particular power injector configuration is illustrated in FIG. 1B,is identified by a reference numeral 240, and is at least generally inaccordance with the power injector 210 of FIG. 1A. The power injector240 includes a powerhead 250 (having a housing) that is mounted on aportable stand 248. Two syringes 286 a, 286 b for the power injector 240are mounted on the powerhead 250. Fluid may be discharged from thesyringes 286 a, 286 b during operation of the power injector 240.

The portable stand 248 may be of any appropriate size, shape,configuration, and/or type. Wheels, rollers, casters, or the like may beutilized to make the stand 248 portable. The powerhead 250 could bemaintained in a fixed position relative to the portable stand 248.However, it may be desirable to allow the position of the powerhead 250to be adjustable relative to the portable stand 248 in at least somemanner. For instance, it may be desirable to have the powerhead 250 inone position relative to the portable stand 248 when loading fluid intoone or more of the syringes 286 a, 286 b, and to have the powerhead 250in a different position relative to the portable stand 248 forperformance of an injection procedure. In this regard, the powerhead 250may be movably interconnected with the portable stand 248 in anyappropriate manner (e.g., such that the powerhead 250 may be pivotedthrough at least a certain range of motion, and thereafter maintained ina desired position).

It should be appreciated that the powerhead 250 could be supported inany appropriate manner. For instance, instead of being mounted on aportable structure, the powerhead 250 could be interconnected with asupport assembly, that in turn is mounted to an appropriate structure(e.g., ceiling, wall, floor). A support assembly for the powerhead 250may be positionally adjustable in at least some respect (e.g., by havingone or more support sections that may be repositioned relative to one ormore other support sections), or may be maintained in a fixed position.Moreover, the powerhead 250 may be integrated with any such supportassembly so as to either be maintained in a fixed position or so as tobe adjustable relative the support assembly.

The powerhead 250 includes a graphical user interface or GUI 252. ThisGUI 252 may be configured to provide one or more (including anycombination) of the following functions: controlling one or more aspectsof the operation of the power injector 240; inputting/editing one ormore parameters associated with the operation of the power injector 240;and displaying appropriate information (e.g., associated with theoperation of the power injector 240). The power injector 240 may includea console 242 and powerpack 246 that each may be in communication withthe powerhead 250 in any appropriate manner (e.g., via one or morecables). The console 242 may be placed on a table or mounted on anelectronics rack in an examination room or a control room, or at anyother appropriate location. The powerpack 246 may be placed on a tableor a floor in an examination room or a control room, or at any otherappropriate location. The powerpack 246 may include one or more of thefollowing and in any appropriate combination: a power supply for theinjector 240; interface circuitry for providing communication betweenthe console 242 and powerhead 250; circuitry for permitting connectionof the power injector 240 to remote units such as remote consoles,remote hand or foot control switches, or other original equipmentmanufacturer (OEM) remote control connections (e.g., to allow for theoperation of power injector 240 to be synchronized with the x-rayexposure of an imaging system); and any other appropriate componentry.The console 242 (which may include a touch screen display 244 or anyother appropriate display and user input device) may provide one or moreof the following functions and in any appropriate combination: allowingan operator to remotely control one or more aspects of the operation ofthe power injector 240; allowing an operator to enter/edit one or moreparameters associated with the operation of the power injector 240;allowing an operator to specify and store programs for automatedoperation of the power injector 240 (which can later be automaticallyexecuted by the power′injector 240 upon initiation by the operator); anddisplaying any appropriate information relation to the power injector240 and including any aspect of its operation.

Various details regarding the integration of the syringes 286 a, 286 bwith the powerhead 250 are presented in FIG. 1C. Each of the syringes286 a, 286 b includes the same general components. The syringe 286 aincludes plunger or piston 290 a that is movably disposed within asyringe barrel 288 a. Movement of the plunger 290 a along an axis 295 a(FIG. 1B) via operation of the powerhead 250 will discharge fluid fromwithin a syringe barrel 288 a through a nozzle 289 a of the syringe 286a. An appropriate conduit (not shown) will typically be fluidlyinterconnected with the nozzle 289 a in any appropriate manner to directfluid to a desired location (e.g., a patient). Similarly, the syringe286 b includes plunger or piston 290 b that is movably disposed within asyringe barrel 288 b. Movement of the plunger 290 b along an axis 295 b(FIG. 1B) via operation of the powerhead 250 will discharge fluid fromwithin the syringe barrel 288 b through a nozzle 289 b of the syringe286 b. An appropriate conduit (not shown) will typically be fluidlyinterconnected with the nozzle 289 b in any appropriate manner to directfluid to a desired location (e.g., a patient).

The syringe 286 a is interconnected with the powerhead 250 via anintermediate faceplate 296 a. This faceplate 296 a includes a cradle 297that supports at least part of the syringe barrel 288 a, and which mayprovide/accommodate any additional functionality or combination offunctionalities. For instance, componentry of a data reader may beincluded in the cradle 297 to facilitate the reading of data from a datastorage device associated with the syringe 286 a. As another example,the cradle 297 may include a heating mechanism that can be used to warmfluid within the syringe 286 a while the syringe 286 a is mounted to thepowerhead 250. A mounting 282 a is disposed on and is fixed relative tothe powerhead 250 for interfacing with the faceplate 296 a. A ramcoupler 276 of a ram 274 (FIG. 10), which are each part of a syringeplunger drive assembly or syringe plunger driver 256 (FIG. 1D) for thesyringe 286 a, is positioned in proximity to the faceplate 296 a whenmounted on the powerhead 250. Details regarding the syringe plungerdrive assembly 256 will be discussed in more detail below in relation toFIG. 1D. Generally, the ram coupler 276 may be coupled with the syringeplunger 290 a of the syringe 286 a, and the ram coupler 276 and ram 274(FIG. 10) may then be moved relative to the powerhead 250 to move thesyringe plunger 290 a along the axis 295 a (FIG. 1B). It may be suchthat the ram coupler 276 is engaged with, but not actually coupled to,the syringe plunger 290 a when moving the syringe plunger 290 a todischarge fluid through the nozzle 289 a of the syringe 286 a.

The faceplate 296 a may be moved at least generally within a plane thatis orthogonal to the axes 295 a, 295 b (associated with movement of thesyringe plungers 290 a, 290 b, respectively, and illustrated in FIG.1B), both to mount the faceplate 296 a on and remove the faceplate 296 afrom its mounting 282 a on the powerhead 250. The faceplate 296 a may beused to couple the syringe plunger 290 a with its corresponding ramcoupler 276 on the powerhead 250. In this regard, the faceplate 296 aincludes a pair of handles 298 a. Generally and with the syringe 286 abeing initially positioned within the faceplate 296 a, the handles 298 amay be moved to in turn move/translate the syringe 286 a at leastgenerally within a plane that is orthogonal to the axes 295 a, 295 b(associated with movement of the syringe plungers 290 a, 290 b,respectively, and illustrated in FIG. 1B). Moving the handles 298 a toone position moves/translates the syringe 286 a (relative to thefaceplate 296 a) in an at least generally downward direction to coupleits syringe plunger 290 a with its corresponding ram coupler 276. Movingthe handles 298 a to another position moves/translates the syringe 286 a(relative to the faceplate 296 a) in an at least generally upwarddirection to uncouple its syringe plunger 290 a from its correspondingram coupler 276.

The syringe 286 b is interconnected with the powerhead 250 via anintermediate faceplate 296 b. A mounting 282 b is disposed on and isfixed relative to the powerhead 250 for interfacing with the faceplate296 b. A ram coupler 276 of a ram 274 (FIG. 10), each of which is partof a syringe plunger drive assembly 256 for the syringe 286 b, ispositioned in proximity to the faceplate 296 b when mounted to thepowerhead 250. Details regarding the syringe plunger drive assembly 256will be discussed in more detail below in relation to FIG. 1D.Generally, the ram coupler 276 may be coupled with the syringe plunger290 b of the syringe 286 b, and the ram coupler 276 and ram 274 (FIG.10) may be moved relative to the powerhead 250 to move the syringeplunger 290 b along the axis 295 b (FIG. 1B). It may be such that theram coupler 276 is engaged with, but not actually coupled to, thesyringe plunger 290 b when moving the syringe plunger 290 b to dischargefluid through the nozzle 289 b of the syringe 286 b.

The faceplate 296 b may be moved at least generally within a plane thatis orthogonal to the axes 295 a, 295 b (associated with movement of thesyringe plungers 290 a, 290 b, respectively, and illustrated in FIG.1B), both to mount the faceplate 296 b on and remove the faceplate 296 bfrom its mounting 282 b on the powerhead 250. The faceplate 296 b may beused to couple the syringe plunger 290 b with its corresponding ramcoupler 276 on the powerhead 250. In this regard, the faceplate 296 bmay include a handle 298 b. Generally and with the syringe 286 b beinginitially positioned within the faceplate 296 b, the syringe 286 b maybe rotated along its long axis 295 b (FIG. 1B) and relative to thefaceplate 296 b. This rotation may be realized by moving the handle 298b, by grasping and turning the syringe 286 b, or both. This rotationmoves/translates both the syringe 286 b and the faceplate 296 b at leastgenerally within a plane that is orthogonal to the axes 295 a, 295 b(associated with movement of the syringe plungers 290 a, 290 b,respectively, and illustrated in FIG. 1B). Rotating the syringe 286 b inone direction moves/translates the syringe 286 b and faceplate 296 b inan at least generally downward direction to couple the syringe plunger290 b with its corresponding ram coupler 276. Rotating the syringe 286 bin the opposite direction moves/translates the syringe 286 b andfaceplate 296 b in an at least generally upward direction to uncoupleits syringe plunger 290 b from its corresponding ram coupler 276.

Each of the faceplates 296 a, 296 b may be characterized as a syringemount—a structure that allows a syringe to be installed on the powerhead250 (e.g., via a detachable connection where a syringe may be attachedto and removed from the powerhead 250 without damaging either thesyringe or the powerhead 250). Generally, such a syringe mount may befurther characterized as at least substantially immobilizing the body orbarrel of a syringe such that the drive ram 274 of the injector 240 canmove the corresponding syringe plunger within and relative to thecorresponding syringe barrel.

As illustrated in FIG. 1C, the syringe plunger 290 b includes a plungerbody 291 and a syringe plunger coupler 292. This syringe plunger coupler292 includes a shaft 294 that extends from the plunger body 291, alongwith a head 293 that is spaced from the plunger body 291. Each of theram couplers 276 includes a larger slot that is positioned behind asmaller slot on the face of the ram coupler 276. The head 293 of thesyringe plunger coupler 292 may be positioned within the larger slot ofthe ram coupler 276, and the shaft 294 of the syringe plunger coupler292 may extend through the smaller slot on the face of the ram coupler276 when the syringe plunger 290 b and its corresponding ram coupler 276are in a coupled state or condition. The syringe plunger 290 a mayinclude a similar syringe plunger coupler 292 for interfacing with itscorresponding ram coupler 276.

The powerhead 250 is utilized to discharge fluid from the syringes 286a, 286 b in the case of the power injector 240. That is, the powerhead250 provides the motive force to discharge fluid from each of thesyringes 286 a, 286 b. One embodiment of what may be characterized as asyringe plunger drive assembly or syringe plunger driver is illustratedin FIG. 1D, is identified by reference numeral 256, and may be utilizedby the powerhead 250 to discharge fluid from each of the syringes 286 a,286 b. A separate syringe plunger drive assembly 256 may be incorporatedinto the powerhead 250 for each of the syringes 286 a, 286 b. In thisregard and referring back to FIGS. 1B-C, the powerhead 250 may includehand-operated knobs 280 a and 280 b for use in separately controllingeach of the syringe plunger drive assemblies 256.

Initially and in relation to the syringe plunger drive assembly 256 ofFIG. 1D, each of its individual components may be of any appropriatesize, shape, configuration and/or type. At least part of the syringeplunger drive assembly 256 is disposed within the powerhead 250. Thesyringe plunger drive assembly 256 includes a motor 258, which has anoutput shaft 260. A drive gear 262 is mounted on and rotates with theoutput shaft 260 of the motor 258. The drive gear 262 is engaged or isat least engageable with a driven gear 264. This driven gear 264 ismounted on and rotates with a drive screw or shaft 266. The axis aboutwhich the drive screw 266 rotates is identified by reference numeral268. One or more bearings 272 appropriately support the drive screw 266.

A carriage or ram 274 is movably mounted on the drive screw 266. Atleast part of this ram 274 may be characterized as being disposed withinthe powerhead 250 (or as being disposed within a housing of thepowerhead 250), although part of the ram 274 extends beyond thepowerhead 250 on a discharge stroke. Generally, rotation of the drivescrew 266 in one direction axially advances the ram 274 along the drivescrew 266 (and thereby along axis 268) in the direction of thecorresponding syringe 286 a/b (e.g., a discharge stroke direction),while rotation of the drive screw 266 in the opposite direction axiallyadvances the ram 274 along the drive screw 266 (and thereby along axis268) away from the corresponding syringe 286 a/b (e.g., a fluid loadingdirection). In this regard, the perimeter of at least part of the drivescrew 266 includes helical threads 270 that interface with at least partof the ram 274. The ram 274 is movably mounted within an appropriatebushing 278 that does not allow the ram 274 to rotate during a rotationof the drive screw 266. Therefore, the rotation of the drive screw 266provides for an axial movement of the ram 274 in a direction determinedby the rotational direction of the drive screw 266.

The ram 274 includes a coupler 276 that that may be detachably coupledwith a syringe plunger coupler 292 of the syringe plunger 290 a/b of thecorresponding syringe 286 a/b. When the ram coupler 276 and syringeplunger coupler 292 are appropriately coupled, the syringe plunger 290a/b moves along with ram 274. FIG. 1D illustrates a configuration wherethe syringe 286 a/b may be moved along its corresponding axis 295 a/bwithout being coupled to the ram 274. When the syringe 286 a/b is movedalong its corresponding axis 295 a/b such that the head 293 of itssyringe plunger 290 a/b is aligned with the ram coupler 276, but withthe axes 268 still in the offset configuration of FIG. 1D, the syringe286 a/b may be translated within a plane that is orthogonal to the axis268 along which the ram 274 moves. This establishes a coupled engagementbetween the ram coupler 276 and the syringe plunger coupler 293 in theabove-noted manner.

Referring now to FIG. 2A, an injector 10 includes a syringe mount 12 tofacilitate attachment of a syringe 14 to the injector 10 in alignmentwith a drive ram 16, in order to provide an injection assembly. Thesyringe 14 for use with the injector 10 generally includes a body 18(which may be in the form of an exterior cylindrical barrel), which atits forward end 20, is integral with a conical front wall 22. A neck 24,terminating in a discharge tip 26, generally extends forwardly from andmay be integral with the conical front wall 22. The body 18 of thesyringe 14 may interface with an interior wall of a pressure jacket (notshown) or a cradle 30 when such a pressure jacket or cradle 30 ispresent on the injector 10. The syringe 14, as used in conjunction withthe injector 10, includes a syringe mating section 32, which may be inthe form of a radially outwardly extending flange 34. This flange 34 ispositioned in a plane substantially perpendicular to a longitudinal axis36 of the syringe 14 and may generally be integral with the rearward end38 of the body 18 of the syringe 14. When the syringe 14 is associatedwith the injector 10, the flange 34 is positioned into and/or in contactwith the syringe mount 12 located on the forward end 40 of a housing 42of the injector 10. The syringe mating section 32 and syringe mount 12may be utilized to facilitate operative connection of the syringe 14 tothe injector 10, as will be described in greater detail below.

Referring now to FIGS. 2A, 4B, and 5B, the discharge tip 26 of thesyringe 14 has an orifice 44 defined in its remote end, which maycommunicate with an internal syringe cavity 46 defined within the neck24, the conical front wall 22, and the body 18 of the syringe 14. Arearward end 48 of the cavity 46 may be defined by a generally forwardfacing surface 50 of a syringe plunger 52. In the illustratedembodiment, this forward facing surface 50 is substantially conical. Thesurface 50 may be of a slope that conforms to the slope of the interiorof the conical front wall 22. The syringe plunger 52 may be snuglyslidable within the body 18 of the syringe 14 such that the cavity 46 isof variable volume. Tubing 28 may be operatively connected to thedischarge tip 26 (e.g., using an appropriate luer fitting) such thatfluid can be expressed from the syringe 14 through the tubing 28.

When the syringe 14 is attached to the injector 10, the syringe plunger52 is preferably located proximal to and in substantial alignment withthe drive ram 16 of the injector 10. The drive ram 16 is driven by amotor (not shown) to move in a forward or rearward motion along itslongitudinal axis 54 to deploy the drive ram 16, and thus toresponsively deploy the syringe plunger 52 in a forward or rearwardmotion along the longitudinal axis 36 of the syringe 14, to inject fluidinto a patient or to fill the syringe 14 with fluid, respectively. Forexample, one may load a prefilled syringe into the injector 10 and, bydeploying the plunger 52 in a forward direction, may thereby expel fluidfrom the syringe 14. In so doing, the fluid may be injected into thepatient. Alternatively, an empty syringe may be loaded into the injector10 while the syringe plunger 52 may be located at or near itsforward-most position. Thereafter, fluid (e.g., contrast media) may beloaded into the syringe 14 by operatively connecting the syringe 14 to asource of fluid and retracting the syringe plunger 52 in a rearwarddirection in order to draw fluid into the syringe 14. As anotheralternative, an empty syringe may be loaded into the injector 10 whilethe syringe plunger 52 may be located at or near its rearward-mostposition. The plunger 52 of the syringe 14 may thereafter be deployed ina forward direction to expel gas (e.g., air) from the syringe 14 (whichis sometimes referred to the art as “initializing” a syringe) inpreparation for a subsequent filling procedure. Subsequently, fluid(e.g., contrast media) may be loaded into the syringe 14 by operativelyconnecting the syringe 14 to a source of fluid and retracting thesyringe plunger 52 in a rearward direction in order to draw fluid intothe syringe 14.

The injector 10 may be designed to accommodate prefilled syringes orempty syringes of varying volumes. For example, the injector 10 may beadapted to receive 125 ml prefilled syringes (e.g., Ultraject® syringecommercially available from Mallinckrodt Inc. of St. Louis, Mo.). Suchsyringes may be used for injecting contrast media into a patient. These125 ml syringes may be prefilled with any of a range of appropriateamounts of fluid, such as 50 ml, 75 ml, 100 ml, 125 ml, or other amount.Additionally, the injector 10 may accommodate an empty syringe of any ofa variety of sizes (e.g., 50 ml, 75 ml, 100 ml, 125 ml, 130 ml, 150 ml,200 ml, etc.).

Referring now to FIGS. 2A-5B, one embodiment of a syringe mount 12 isshown. The syringe mount 12 is a structure that allows the syringe 14 tobe installed on the injector 10 (e.g., via a detachable connection wherethe syringe 14 may be attached to and removed from the injector 10without damaging either the syringe 14 or the injector 10). Generally,the syringe mount 12 may be further characterized as at leastsubstantially immobilizing the body or barrel 18 of the syringe 14 suchthat the drive ram 16 of the injector 10 can move the syringe plunger 52within and relative to the syringe barrel 18.

The syringe mount 12 includes a movable actuator 56 including a wallmember 58 defining an orifice 60, and at least a first movable member 62operatively coupled to the actuator 56 and responsively movabletherewith. More specifically, the syringe mount 12 of the illustratedembodiment includes first and second movable members 62, 64 that areoperatively coupled to the wall member 58 of the actuator 56. The firstand second movable members 62, 64 include first and second pins 66, 68operatively connected thereto. The first pin 66 is operatively couplednear a first end 70 of the first movable member 62, and the second pin68 is operatively coupled near a first end 72 of the second movablemember 64. The first and second pins 66, 68 are received in at least oneslot 74 defined in the wall member 58 of the actuator 56, to couple thefirst and second movable members 62, 64 thereto. The actuator 56 isdisposed proximally of the first and second movable members 62, 64.Further, the first and second members 62, 64 may include first andsecond rods 67, 69 projecting rearwardly therefrom. These first andsecond rods 67, 69 may confront and move along the outer contour of thewall member 58 of the actuator 56, as the first and second movablemembers 62, 64 move between open and closed positions.

The slot 74 is defined by the wall member 58 of the actuator 56 at abase portion 76 thereof. The first and second pins 66, 68 are movable(e.g., slidable and optionally rotatable) within the slot 74. Each ofthe first and second pins 66, 68 can move from a position proximal tothe center 78 of the slot 74, to positions near first and secondterminal ends 80, 82 of the slot 74. The first and second pins 66, 68 donot both move on one side of the slot 74. Rather, the first pin 66 isadapted to move within one portion of the slot 74, and the second pin 68is adapted to move within another portion of the slot 74. In particular,in the illustrated embodiment, a base portion 76 of the wall member 58includes an opening 84 having a top portion thereof in a shape at leastgenerally similar to a “V.” The first and second pins 66, 68 aredisposed in the “V” portion of this opening 84. When the first andsecond pins 66, 68 are positioned near the intersection of the two legsof the “V,” the first and second movable members 62, 64 are in an openposition (see FIG. 4A). When the first and second pins 66, 68 arepositioned near the first and second terminal ends 80, 82 of the “V,”the first and second movable members 62, 64 are in a closed position(see FIG. 5A). While the slot 74 of the illustrated embodiment is shownand described here as generally having a “V” shape, it will berecognized by those skilled in the art that such a “V” shape is notnecessary, and any other shape can be used that allows the first andsecond movable members 62, 64 to move sufficiently within a slot tooperatively connect a syringe to an injector 10. For example, the slot74 may have a “U” or “C” shape. Those skilled in the art will recognizethat more than one slot may be used. For example, two slots forming a“V” shape proximal to the base 76 of the wall member 58 can receive thefirst and second pins 66, 68 near the point of the “V.” Those skilled inthe art will recognize that the slots do not necessarily have to be inthe shape of a “V.”

As can be seen from FIGS. 2A-5S, the actuator 56 and the first andsecond movable members 62, 64 of the syringe mount 12 are held within aface plate 86 of the housing 42 of the injector 10 (additional views ofthe face plate may be seen in FIGS. 6-12). Referring particularly toFIG. 2C, the face plate 86 includes a proximal wall portion 88, a distalwall portion 90, a cradle 30 extending distally from the distal wallportion 90, and a coupling plate 92. The first and second movablemembers 62, 64 are located between the coupling plate 92 and the wallmember 58 of the actuator 56, and all three components are thencontained within an interior cavity 94 of the face plate 86, formedbetween the proximal wall portion 88 and distal wall portion 90. Theactuator 56 and the first and second movable members 62, 64 are movablewithin the interior cavity 94. The coupling plate is preferablysubstantially immobile relative to the proximal and distal wall portionsof the face plate 86, as it is preferably fixed to at least one of theproximal and distal wall portions 88, 90. In the illustrated embodiment,this fixing occurs through the use of screws 96, which extend throughorifices 97 in a rear plate 99, orifices 98 in the proximal wall portion88, orifices 100 in the coupling plate 92, and are received in orifices(not shown) in the distal wall portion 90.

The coupling plate 92 includes first and second pivoting shafts 101, 103projecting from a proximal surface 105 thereof. These first and secondpivoting shafts 101, 103 are received in first and second shaft openings107, 109 defined in the first and second movable members 62, 64,respectively. As such, the first and second movable members 62, 64 areable to exhibit a pivoting motion about the corresponding first andsecond pivot shafts 101, 103. Stated another way, the first and secondmovable members 62, 64 are coupled with corresponding the first andsecond pivoting shafts 101, 103 in a manner such that the movablemembers 62, 64 can pivot thereabout. The first and second pivotingshafts 101, 103 thus may be said to provide pivot points for the firstand second movable members 62, 64.

To initiate loading of the syringe 14 into the syringe mount 12, theflange 34 at the rearward end 38 of the syringe 14 may be passed throughan aperture in each of the distal wall portion 90 of the syringe mount12 and the coupling plate 92 and may be received into the orifice 60defined in the actuator 56. While the rearward end 38 of the syringe 14is located in the orifice 60, the syringe 14 may be moved in a firstdirection substantially perpendicular to the longitudinal axis 54 of thedrive ram 16 of the injector 10. Herein, this direction will be referredto as a “downward” direction (as the motion is down relative to theinjector 10). However, it will be recognized by those skilled in the artthat the motion does not have to be “downward,” but that the componentsof the syringe mount 12 can be configured such that motion in otherdirections can effect appropriate engagement of the syringe 14(including, but not limited to, “upward” movement, “side-to-side”movement, or any other appropriate, substantially perpendicular movementsuch that the longitudinal axis 36 of the syringe 14 is moved into asubstantially coaxial relationship with the longitudinal axis 54 of thedrive ram 16). This downward motion, in turn, responsively moves theactuator 56 in the downward direction. The motion of the actuator 56 inthe downward direction causes each of the first and second pins 66, 68to move to the corresponding first and second ends 80, 82 of the slot 74defined in the base portion 76 of the wall member 58. This movement ofthe pins 66, 68 occurs because the first and second movable members 62,64 cannot move in the downward direction due to the first and secondpivoting shafts 101, 103 of the fixed coupling plate 92 being locatedwithin the first and second shaft openings 107, 109 of the first andsecond movable members 62, 64. Thus, as the actuator 56 moves in thedownward direction, the first and second pins 66, 68 move within theslot 74 to the first and second terminal ends 80, 82 thereof. Becausethe first and second movable members 62, 64 cannot move downwardly, theyinstead pivot about the pivot points provided by the first and secondpivoting shafts 101, 103. In other words, the first and second movablemembers 62, 64 rotate about the corresponding first and second pivotingshafts 101, 103 at the respective first and second shaft openings 107,109. As such, the first and second movable members 62, 64 pivot toengage (e.g., substantially, circumferentially envelop) the rearward end38 of the syringe 14 (see FIG. 5A). Since the flange 34 of the syringe14 is located within the actuator 56 during this pivoting movement ofthe movable members 62, 64, the first and second movable members 62, 64engage the body 18 of the syringe 14 (rather than the flange 34). Inembodiments where the movable members 62, 64 are designed such that thisengagement with the body 18 of the syringe 14 may be characterized as asubstantial enveloping of the body 18, it may be said that this type ofengagement allows for greater coverage of the syringe 14 than found inprior syringe mounts, and thus, potentially allows the syringe 14 towithstand greater injection pressures.

In the illustrated embodiment, the first and second movable members 62,64 are opposite one another and are positioned about the longitudinalaxis 54 of the drive ram 16. The first and second movable members 62, 64each have an arcuate face 102, 104. These arcuate faces 102, 104 areshown as being diametrically opposite one another and located exteriorto the body 18 of the syringe 14. When the syringe 14 is properlyengaged with the syringe mount 12 of the injector 10, the first andsecond movable members 62, 64 of the syringe mount 12 are in contactwith the side surface of the exterior body 18 of the syringe 14 to holdthe syringe 14 in place and in alignment with the drive ram 16 of theinjector 10.

In some embodiments, the arcuate faces 102, 104 of the movable members62, 64 may bear one or more types of engagement enhancing features(e.g., grooves, bumps, indentations, ridges, teeth, combinationsthereof, and the like) to improve the ability of the movable members 62,64 to grip and/or hold the syringe 14. In some embodiments, a gripenhancing coating (e.g., Santoprene® elastomer) may be applied to thearcuate faces 102, 104 of the movable members 62, 64 to facilitategripping/holding of the syringe 14.

The pivotal movement of the first and second movable members 62, 64alters the distance between the arcuate faces 102, 104 as they pivottoward and away from one another. In the illustrated embodiment, thefirst and second movable members 62, 64 are each movable. In someembodiments, it is possible to use a single movable member disposed inspaced relation to an immobile member (e.g., arcuate stop or abutment)toward which the single movable member may be moved.

In some embodiments, first and second movable members 62, 64 are notnecessary for appropriate syringe engaging function. In suchembodiments, a single gripping member may be used to engage the syringe14, thereby operatively connecting the syringe 14 to the injector 10. Insuch embodiments, the single movable member should cover enough of thecircumference of the syringe 14, when in contact with the body 18, tohold the syringe 14 against the injector 10. In such embodiments, eacharm extending from a center point of the movable member may have adegree of elasticity such that the arms may splay outwardly and inwardlyto allow for insertion and/or removal of the syringe 14.

The wall member 58 of the actuator 56 is shown as having a peripheralside surface 110 that includes a first undulating contour 106 and asecond undulating contour 108. As shown, the second undulating contour108 is positioned substantially opposite the first undulating contour106. Each of these first and second undulating contours 106, 108includes a first valley 112, a second valley 114, and a ridge 116disposed therebetween. When positioned within the syringe mount 12 ofthe injector 10, these first and second undulating contours 106, 108 areconfronted by first and second projections 118, 120 (see FIGS. 2C and5A), which are adapted to ride along the surface of the first and secondundulating contours 106, 108 as the actuator 56 is moved between thefirst and second positions. In the illustrated embodiment, the first andsecond projections 118, 120 are coupled to the proximal wall portion 88of the face plate 86, and are spring-biased in a direction toward eachof the first and second undulating contours 106, 108. The interaction ofthe first and second detents 118, 120 and first and second undulatingcontours 106, 108 assist in maintaining the actuator 56 in either thefirst or second position until a user desires to move the actuator 56 toeither load or unload the syringe 14. In some embodiments, the first andsecond pins 66, 68 may include bias springs associated with each of thefirst and second movable members 62, 64. In such embodiments, one end ofeach of the bias springs may be in contact with its respectivelyassociated movable member, and the opposite end of each bias spring mayseat or bear against portions of the housing 42 (or face plate 86) ofthe injector 10. In some embodiments, at least a portion of these biassprings may be disposed about the pins 66, 68, which form the pivot axesof the first and second movable members 62, 64.

To load a syringe 14 into the injector 10, the syringe 14 is positionedrelative to the wall member 58 of the actuator 56 such that the flange34 at the rearward end 38 of the syringe 14 is received within theorifice 60 of the wall member 58 such that at least one contact point122 on the periphery of the flange 34 contacts or can be brought intocontact with a peripheral surface 124 defining the orifice 60. Morespecifically, the flange 34, in certain embodiments, may be received bya recess 125 in the actuator 56. The actuator 56 is shown in FIG. 4A asbeing in the first position, such that the first and second movablemembers 62, 64 are in the open position. In this first position, thefirst and second projections 118, 120 are in contact with the firstvalleys 112 of the corresponding first and second undulating contours106, 108. The force of the spring bias of the first and secondprojections 118, 120 at least assists in preventing the wall member 58of the actuator 56 from moving unassisted to the second position. Thedrive ram 16 of the injector 10 is preferably positioned such that aplunger coupling mechanism 126 is aligned with a coupling mechanism 128extending from a rearward face of the syringe plunger 52 (see FIG. 4B).

A user then applies a force to the syringe 14 in a directionsubstantially perpendicular to, and towards, the longitudinal axis 54 ofthe drive ram 16. The flange 34 of the syringe 14, contacting theperipheral surface 124 of the wall member 58, is utilized to force thewall member 58 of the actuator 56 to responsively move in a directionsubstantially perpendicular to the longitudinal axis 54 of the drive ram16. Enough force is applied to overcome the spring-bias of the first andsecond projections 118, 120, such that the actuator 56 moves from thefirst position to the second position. As this occurs, the first andsecond projections 118, 120 ride along the first and second undulatingcontours 106, 108 from the first valleys 112, along the ridges 116, andinto the second valleys 114. The first and second projections 118, 120may then be utilized to at least assist in maintaining the wall member58 in the second position shown in FIG. 5A.

The movement of the wall member 58 from the first position to the secondposition cooperatively moves the slot 74 of the wall member 58 in adirection substantially perpendicular to the longitudinal axis 54 of thedrive ram. And thus, the slot 74 moves relative to the first and secondpins 66, 68, thereby causing the first and second pins 66, 68 to moverelative to and within the slot 74. More specifically, in theillustrated embodiment, the first and second pins 66, 68 move within theV-shaped slot from a position proximal to the point of the “V,” topositions proximal to the terminal ends of each leg of the “V” (from theposition shown in FIG. 4A, to the position shown in FIG. 5A). Thismovement causes a responsive pivotal movement of the first and secondmovable members 62, 64 from the open position to the closed positionsuch that the rearward end 38 of the syringe 14 is engaged by the firstand second movable members 62, 64. In particular, as the actuator 56moves in the downward direction, the first and second pins 66, 68 movewithin the slot 74 to the first and second terminal ends 80, 82 thereof.Because the first and second movable members 62, 64 cannot movedownwardly, they instead pivot about the pivot points provided by thefirst and second pivoting shafts 101, 103. In other words, the first andsecond movable members 62, 64 rotate about the first and second pivotingshafts 101, 103 at the first and second shaft openings 107, 109,respectively.

As the wall member 58 is moved from the first position to the secondposition, and the syringe 14 moves with the wall member 58 from aposition not engaged by the movable members 62, 64 to a position engagedby the movable members 62, 64, the coupling mechanism 128 at therearward end 38 of the syringe plunger 52 moves from a position notengaged with the plunger coupling mechanism 126 of the drive ram 16 to aposition engaged with the plunger coupling mechanism 126 of the driveram 16. In the illustrated embodiment (see FIGS. 4B and 5B), when theflange 34 of the syringe 14 is aligned with the orifice 60 defined bythe wall member 58, the syringe plunger 52 within the syringe 14 ispreferably positioned such that the coupling mechanism 128 on therearward face of the syringe plunger 52 is aligned with the plungercoupling mechanism 126 of the drive ram 16. The coupling mechanism 128of the illustrated syringe plunger 52 is a projection 128 extending fromthe rearward face of the syringe plunger 52. This projection 128 may becharacterized as exhibiting a “T” shape having a stem portion 130(parallel to the longitudinal axis 36 of the syringe 14) topped by a capportion 132 (transverse to the longitudinal axis of the syringe 14). Asthe wall member 58 is moved from the first position to the secondposition, the cap portion 132 of the coupling mechanism 128 may bereceived by the plunger coupling mechanism 126, which in the illustratedembodiment, is a slot 134 formed in the forward end of the drive ram 16.

A slot 134 is defined in the forward end of the drive ram 16 in a shapeto receive the coupling mechanism 128 of the syringe 14, andparticularly the cap portion 132 thereof. A cross-section of the plungercoupling element 126 is shown as exhibiting a J-shape (having a slotwithin a hook portion of the “J” configured to receive the cap portion132), such that when the syringe plunger 52 is engaged with the driveram 16, the distal end 136 of the “J” shape is positioned distally of apart of the cap portion 132 of the coupling mechanism 128. Thus, whenthe syringe 14 is initially inserted into the actuator 56 (in the firstposition), the cap portion 132 of the coupling mechanism 128 is “above”the plunger coupling element 126 of the drive ram 16. However, as theactuator 56 is moved to the second position, the cap portion 132 of thecoupling mechanism 128 is moved to be positioned proximally of thedistal end 136 of the plunger coupling mechanism 126 of the drive ram16. Once engaged, an injection procedure may be run, such as bytranslating the drive ram 16 forward along its longitudinal axis 54 todispense a fluid, such as contrast media, from the syringe 14. While theslot 134 and extension 128 of the illustrated embodiment have shapesreferred to herein as “J” and “T,” respectively, it will be recognizedby those of skill in the art that any shape that facilitates couplingmay be used. Additionally, while the illustrated embodiment depictsfirst a coupling mechanism 128 and plunger coupling mechanism 126 thatresult in a passive coupling, those of skill in the art will recognizethat coupling mechanisms and plunger coupling mechanisms that result inan active coupling (one which involves some degree of positive gripping)may be used.

As described previously, the syringe mount 12 allows for the syringe 14to be removed from the face plate 86 and/or forward end 40 of theinjector 10, when the drive ram 16 of the injector 10 is at anyposition. It does not require the drive ram 16 to be returned to a“home” position before detaching the syringe 14 from the injector 10.Thus, during an injection procedure, the translation of the drive ram 16may be stopped while the drive ram 16 is in an extended position fromthe front face place 86 of the injector 10. A user can then grip thesyringe 14 and move it in an upward direction, thereby overcoming thespring-biased force of the first and second projections 118, 120 tocause the actuator 56 to move from the second position to the firstposition. As this occurs, the first and second projections 118, 120 ridealong the first and second undulating contours 106, 108 from the secondvalleys 114, over the ridges 116, and into the first valleys 112.Simultaneously, the first and second pins 66, 68 of the first and secondmovable members 62, 64 will move within the V-shaped slot of the wallmember 58 from a position near the terminal ends 80, 82 of the arms ofthe V to a position near the point of the V. This causes the first andsecond movable members 62, 64 to pivot from the closed position to theopen position by pivoting about the pivot points created by theinteraction of the first and second pivoting shafts 101, 103 with thefirst and second shaft openings 107 109. Due to the positioning of theflange 34 at the rearward end 38 of the syringe 14 within the orifice 60of the actuator 56, the actuator 56 allows for enough vertical syringemovement for the T-shaped coupling mechanism on the rearward face of thesyringe 14 to clear the slot on the forward end of the drive ram 16,thereby allowing removal of the syringe 14 from the injector 10.

The power injectors 210, 240, and 10 of FIGS. 1A, 1B, and 2A,respectively, each may be used for any appropriate application,including without limitation for medical imaging applications wherefluid is injected into a subject (e.g., a patient). Representativemedical imaging applications for the power injectors 210, 240, 10include without limitation computed tomography or CT imaging, magneticresonance imaging or MRI, SPECT imaging, PET imaging, X-ray imaging,angiographic imaging, optical imaging, and ultrasound imaging. The powerinjectors 210, 240, 10 each could be used alone or in combination withone or more other components. The power injectors 210, 240, 10 each maybe operatively interconnected with one or more components, for instanceso that information may be conveyed between the power injector 210, 240,10 and one or more other components (e.g., scan delay information,injection start signal, injection rate).

Any number of syringes may be utilized by each of the power injectors210, 240, 10, including without limitation single-head configurations(for a single syringe) and dual-head configurations (for two syringes).In the case of a multiple syringe configuration, each power injector210, 240, 10 may discharge fluid from the various syringes in anyappropriate manner and according to any timing sequence (e.g.,sequential discharges from two or more syringes, simultaneous dischargesfrom two or more syringes, or any combination thereof). Multiplesyringes may discharge into a common conduit (e.g., for provision to asingle injection site), or one syringe may discharge into one conduit(e.g., for provision to one injection site) while another syringe maydischarge into a different conduit (e.g., for provision to a differentinjection site). Each such syringe utilized by each of the powerinjectors 210, 240, 10 may include any appropriate fluid, for instancecontrast media, a radiopharmaceutical, saline, and any combinationthereof. Each such syringe utilized by each of the power injectors 210,240, 10 may be installed in any appropriate manner (e.g., rear-loadingconfigurations may be utilized; front-loading configurations may beutilized; side-loading configurations may be utilized).

FIG. 6 is a perspective view of one embodiment of a power injectorsyringe clamp assembly 300, which may be used by the syringe mount 12 ofthe power injector 10 of FIG. 2A (replacing the movable members 62, 64),as well as any other appropriate power injector. Generally, the clampassembly 300 may be used to hold or retain a power injector syringe 330on a powerhead of the corresponding power injector. Although the clampassembly 300 could exert a compressive force on the power injectorsyringe 330, such may not be required in all instances. Instead, one ormore portions of the clamp assembly 300 could be disposed in closelyspaced relation to the power injector syringe 330, one or more portionsof the clamp assembly 300 could simply be disposed in interfacingrelation with the power injector syringe 330, or both. The clampassembly 300 includes at least one RFID antenna for communicating withone or more RFID tags 336 on the power injector syringe 330 (e.g., toread data from one or more RFID tags 336; to write data to one or moreRFID tags 336). Any appropriate number of RFID antennas may be utilizedby the clamp assembly 300, with each RFID antenna being of anyappropriate size, shape, configuration, and/or type (e.g., of anyappropriate layout or pattern). Any appropriate way of providing powerto an RFID antenna of the clamp assembly 300 may be utilized. Anyappropriate way of incorporating one or more RFID antennas with theclamp assembly 300 may be utilized (e.g., separately mounting one ormore RFID antennas to the clamp assembly 300; integrating one or moreRFID antennas into the structure of the clamp assembly 300; andincluding any combination thereof).

Various integrations of an RFID antenna by the clamp assembly 300 willbe discussed below in relation to FIGS. 7-10. Referring first to FIG. 7,there the clamp assembly 300 includes a first clamp member 302 and asecond clamp member 312. The first clamp member 302 and the second clampmember 312 may be characterized as being disposed in opposing relation.In the illustrated embodiment, each clamp member 302, 312 is disposedoutwardly from different portions of the syringe barrel 332 of the powerinjector syringe 330, but at the same location along the lengthdimension of the power injector syringe 330 (the length dimensioncoinciding with an axis 338). The first clamp member 302 includesoppositely disposed end surfaces 304, 306, along with an inner orinterior surface 308. The end surface 306 would project toward or face aflange 334 of the power injector syringe 330 when positioned within theclamp assembly 300 and with the clamp assembly 300 being in a closedconfiguration (a representative closed configuration being shown in FIG.7). That is, the syringe flange 334 would be disposed behind the clampassembly 300 in the view shown in FIG. 6. The inner surface 308 wouldproject toward or face the barrel 332 of the power injector syringe 330when positioned within the clamp assembly 300 and with the clampassembly 300 being in its closed configuration. A first pivot pin 310pivotally interconnects the first clamp member 302 with the powerhead ofthe power injector that is incorporating the clamp assembly 300.

The second clamp member 312 includes oppositely disposed end surfaces314, 316, along with an inner or interior surface 318. The end surface316 would project toward or face the syringe flange 334 of the powerinjector syringe 330 when positioned within the clamp assembly 300 andwith the clamp assembly 300 being in a closed configuration. That is,the syringe flange 334 would be disposed behind the clamp assembly 300in the view shown in FIG. 6. The inner surface 318 would project towardor face the barrel 332 of the power injector syringe 330 when positionedwithin the clamp assembly 300 and with the clamp assembly 300 being inits closed configuration. A second pivot pin 320 pivotally interconnectsthe first clamp member 312 with the powerhead of the power injector thatis incorporating the clamp assembly 300.

The flange 334 of the power injector syringe 330 may be characterized asbeing located at or on a proximal end of the power injector syringe 330(e.g., an oppositely disposed distal end of the power injector syringe330 may accommodate a fluid discharge from the power injector syringe330; the flange 334 being located similarly to the flange 34 of thesyringe 14 shown in FIG. 2A). At least one RFID tag 336 is disposed onthe power injector syringe 330. Each RFID tag 336 may be of anyappropriate size, shape, configuration, and/or type, may be fabricatedin any appropriate manner, may be encoded with any appropriateinformation, and may be disposed at any appropriate location on thepower injector syringe 330. Any appropriate number of RFID tags 336 maybe disposed on the power injector syringe 330, and multiple RFID tags336 may be disposed in any appropriate arrangement. One or more RFIDtags 336 could be disposed on the syringe barrel 332, one or more RFIDtags 336 could be disposed on the flange 334 of the power injectorsyringe 330, or both.

The illustrated embodiment of the clamp assembly 300 allows each of thefirst clamp member 302 and the second clamp member 312 to move betweenat least two general positions to define open and closed configurationsfor the clamp assembly 300. Each of the first clamp member 302 and thesecond clamp member 312 may be moved along any appropriate path orcombination of paths to define open and closed configurations for theclamp assembly 300. Any appropriate way of actuating the clamp assembly300 into each of its open and closed configurations may be utilized. Inone embodiment, a single actuator of any appropriate size, shape,configuration, and/or type (e.g., actuator 56) simultaneously pivots thefirst clamp member 302 and the second clamp member 312 about theirrespective pivot pins 310, 320. It should be appreciated that separateactuators could be provided for each of the first clamp member 302 andthe second clamp member 312. It should be appreciated that one of thefirst clamp member 302 and the second clamp member 312 could actually bemaintained in a stationary or fixed position (at least relative to theother clamp member 302, 312), while the other is moved in anyappropriate manner to provide the open and closed configurations for theclamp assembly 300 (not shown).

FIG. 7 illustrates one option for integrating at least one RFID antennawith the clamp assembly 300. A first RFID antenna section 340 isdisposed on the end surface 304 of the first clamp member 302 (endsurface 306 being another option—not shown), while a second RFID antennasection 342 is disposed on the end surface 314 of the second clampmember 312 (end surface 316 being another option—not shown). The firstRFID antenna section 340 and the second RFID antenna section 342 eachcould be autonomous or independently operable (e.g., fully functional)RFID antennas. Alternatively, the first RFID antenna section 340 and thesecond RFID antenna section 342 may collectively define a single RFIDantenna (at least when the clamp assembly 300 is in the closedconfiguration shown in FIG. 7). Any appropriate layout may be utilizedfor each of the first RFID antenna section 340 and the second RFIDantenna section 342.

Two options for providing power to an RFID antenna integrated with theclamp assembly 300 are illustrated by FIG. 7. Power to the RFID antennasection 340 is provided by a flex connector 344 of any appropriate size,shape, configuration, and/or type. Power to the second RFID antennasection 342 is provided though the second pivot pin 320, which wouldtherefore be formed from an electrically conductive material orcombination of materials.

Another layout for an RFID antenna is illustrated in FIG. 8A. Here anRFID antenna section 350 is disposed on an inner surface 308/318 of thefirst/second clamp member 302/312 (the surface of the clamp member302/312 that projects toward or faces the syringe barrel 332 when thepower injector syringe 330 is positioned within the clamp assembly 300).Although the first/second pivot pins 310/320 are not shown in FIG. 8A,the first/second pivot axis 311/321 is shown in FIG. 8A (the axis311/321 about which the respective first/second clamp member 302/312moves). The RFID antenna section 350 functions itself as an RFID antennain the illustrated embodiment, although it could be configured tocollectively define an RFID antenna with another RFID antenna section onthe other clamp member 302/312 of the clamp assembly 300 (not shown).

FIG. 8B shows another possible layout for an RFID antenna on the powerinjector syringe clamp assembly 300 of FIG. 6. Here a first RFID antennasection 360 and a second RFID antenna section 362 are each disposed onan inner surface 308/318 of the first/second clamp member 302/312 (thesurface of the clamp member 302/312 that projects toward or faces thesyringe barrel 332 when the power injector syringe 330 is positionedwithin the clamp assembly 300). Although the first/second pivot pins310/320 are not shown in FIG. 8B, the first/second pivot axis 311/321 isshown in FIG. 8B (the axis 311/321 about which the respectivefirst/second clamp member 302/312 moves). The RFID antenna sections 360,362 could each function as an RFID antenna in the illustratedembodiment. Each RFID antenna section 360, 362 could collectively definean RFID antenna with another RFID antenna section on the other clampmember 302/312 of the clamp assembly 300 (such that the clamp assembly300 would include two, separate RFID antennas). Finally, each RFIDantenna section 360, 362 could be part of a single RFID antenna for theclamp assembly 300, including where one or more RFID antenna sectionsare disposed on the other clamp member 302/312.

Two ways of providing electrical power to an RFID antenna on the clampassembly 300 were discussed above in relation to FIG. 7. Additionaloptions are presented in FIGS. 9 and 10. In FIG. 9, a pivot pin 370 isconfigured to provide separate electrical connections to the pair ofspaced RFID antenna sections 360, 362 shown in FIG. 8B. The pivot pin370 for the clamp member 302/312 includes a first conductive section 372and a second conductive section 376 that are separated by anintermediate insulator section 374. A pair of movable and electricallyconductive pins 378 are spaced from each other and biased into contactwith the pivot pin 370 in any appropriate manner (e.g., using a springor the like—not shown). One conductive pin 378 engages the firstconductive section 372 of the pivot pin 370, while the other conductivethan 378 engages the second conductive section 376 of the pivot pin 370.Each conductive pin 378 is in electrical contact with its own conductor380, at least when the conductive pins 378 are in contact with the pivotpin 370. One conductor 380 extends to or is otherwise in electricalcommunication with the first RFID antenna section 360, while the otherconductor 380 extends to or is otherwise in electrical communicationwith the second RFID section 362 (see FIG. 8B).

The first/second clamp member 302/312 shown in FIG. 10 includes an RFIDantenna section 380, which in turn includes a pair of legs 382 that arespaced from each other. Each leg 382 extends to an edge 386 of the clampmember 302/312, and is aligned with its own electrical contact 384(e.g., mounted on a powerhead). When the clamp member 302/312 is movedto dispose the clamp assembly 300 into its closed configuration, eachleg 382 is brought into electrical contact with its correspondingelectrical contact 384. The other clamp member 302/312 could have asimilar pair of electrical contacts 384, or the other clamp member302/312 could also be brought into contact with the electrical contacts384 shown in FIG. 10.

A power injector syringe clamp assembly of any appropriate size, shape,configuration and/or type (e.g., including any appropriate number ofclamp members, including utilizing a single clamp member and wheremultiple clamp members are utilized and disposed in any appropriatearrangement) may include at least one RFID antenna in accordance withthe foregoing. In one embodiment, one or more RFID antennas areincorporated by a power injector syringe clamp assembly in a manner suchthat relative positioning requirements between this clamp assembly andan installed power injector syringe are reduced. It may be desirable foreach RFID tag on an installed power injector syringe to be readable byone or more RFID antennas of the power injector syringe clamp assembly,regardless of its position within the power injector syringe clampassembly.

One or more clamp members of the power injector syringe clamp assemblymay include an RFID antenna in accordance with the foregoing. A givenRFID antenna may be incorporated with a single clamp member, or may beincorporated with multiple clamp members. Although each clamp member ofthe power injector syringe clamp assembly could include an RFID antenna,it may be such that one or more clamp members will not have any RFIDantenna included therewith in the case of a multi-clamp memberconfiguration (at least one clamp member, however, will still include atleast one RFID antenna in such an instance).

The various power injector syringe clamp assemblies described herein maybe utilized by any appropriate power injector and may be integrated inany appropriate manner. In one embodiment, the syringe clamp assembly ismounted on a powerhead of the power injector. In another embodiment, thesyringe clamp assembly is incorporated into the structure of a faceplatethat in turn may be detachably mounted (e.g., by hand or without anytools) to a powerhead of a power injector. In yet another embodiment,the syringe clamp assembly is incorporated into the structure of anadapter that in turn is mounted to a powerhead of a power injector.

FIG. 11 presents one embodiment of an imaging suite 400 that includes acontrast media injector system 430, a medical imaging system 407, a datastore 414, and at least one patient renal function data source 438. Oneor more external devices 439 may communicate with the injector system430 and/or the medical imaging system 407. A given device 439 may becharacterized as being “external” if it is not actually part of aparticular system 430 and/or 407. One or more external devices 439 couldalso communicate with the data store 414 and/or one or more patientrenal function data sources 438. Representative external devices 439include without limitation a hospital information system (HIS), aradiology information system (RIS), a picture archive and communicationsystem (PACS), a patient electronic medical records (EMRs) system, orthe like.

The data store 414 may be operatively connected with the contrast mediainjector system 430 and/or the medical imaging system 407 by acommunication link 410 of any appropriate type. The data store 414 couldbe incorporated by the contrast media injector system 430 and/or couldbe incorporated by the medical imaging system 407. A patient renalfunction data source 438 may be operatively connected with the contrastmedia injector system 430 and/or the medical imaging system 407 by acommunication link 410 of any appropriate type.

The medical imaging system 407 includes a remote console 409 and animaging unit or device 422. The contrast media injector system 430 inturn includes a power injector 432 and a remote console 404. The powerinjector 432 may be of any appropriate configuration, for example, inthe form of the power injectors 10 and 210 addressed above. The imagingdevice 422 may be of any appropriate size, shape, configuration, and/ortype, and its image-acquisition functionality may utilize anyappropriate technology or combination of technologies. In theillustrated embodiment, the imaging suite 400 includes a control room402 and an imaging room 420 that are separated by an appropriate barrier412. This separation may not be required in all instances. In someembodiments, this barrier may include radiation (e.g., alpha, betaand/or gamma) shielding, RF shielding, and/or any other type of materialthat may reduce the likelihood of undesired conditions that could hinderimage acquisition.

The remote console 404 (e.g., a computer) of the contrast media injectorsystem 430 may be located in the control room 402. Components of theremote console 404 include a remote console display 406 and at least onedata or user input device 408. Each user input device 408 of theinjector system 430 may be of any appropriate type, for instance, in theform of a keyboard, mouse, touch screen, joystick, trackball, or thelike. The remote console 404 is operatively interconnected with thepower injector 432 by a communication link 410 of any appropriate type.Generally, a user may program injection parameters for the powerinjector 432 (e.g., define an injection protocol, for instance one ormore phases and where each phase includes injection parameters such as avolume of contrast media to be injected and an injection flow rate,along with possibly one or more injection delays (e.g., a hold or apause)) through the user input device 408 of the remote console 404. Anyappropriate data may be entered through the user input device 408.

Similarly, the remote console 409 (e.g., a computer) of the medicalimaging system 407 may be located in the control room 402. Components ofthe remote console 409 may include a remote console display 411 and atleast one data or user input device 413. Each user input device 413 ofthe medical imaging system 407 may be of any appropriate type, forinstance, in the form of a keyboard, mouse, touch screen, joystick,trackball, or the like. The remote console 409 of the imaging system 407is operatively interconnected with the imaging device 422 by acommunication link 410 of any appropriate type. Generally, a user mayprogram imaging parameters for the imaging device 422 and/or control(e.g., initiate and/or terminate) imaging procedures by way of the userinput device 413 of the remote console 409. Any appropriate data may beentered through the user input device 413.

The medical imaging system 407 (e.g., the remote console 409 thereof)may be operatively connected with the contrast media injector system 430(e.g., the remote console 404 thereof). In the case where the imagingsystem 407 is indeed operatively connected with the injector system 430,some embodiments allow for a user to program injection parameters and/orcontrol (e.g., initiate and/or terminate) injection procedures for thepower injector 432 through the user input device 413 of the imagingsystem's remote console 409 in addition to the performing theprogramming and/or control functionalities herein-described with regardto the imaging device 422. In some embodiments of the imaging suite 400,the injector system 430 and the medical imaging system 407 may onlyinclude a single, shared remote console (not shown) from which a usermay perform any of the herein-described program and/or controloperations for both the imaging device 422 and the power injector 432.

The power injector 432 is operatively connected with the remote console404, may be operatively connected with one or both of the data store 414and the imaging device 422, and is fluidly connectable with a patient424 (e.g., such that the power injector 432 may inject contrast mediainto the patient 424). The power injector 432 may include a display 434and at least one data or user input device 436 of any appropriate type(e.g., a keyboard, mouse, touch screen, joystick, trackball, or thelike). Any appropriate data may be entered through the user input device436.

The data store 414 may be of any appropriate configuration and may beincorporated by an appropriate computer-readable storage medium. Thedata store 414 could be a stand-alone component, may be incorporated bythe contrast media injector system 430 in any appropriate manner (e.g.,as part of the remote console 404, as part of the power injector 432, bya stand-alone storage device, or any combination thereof), and/or may beincorporated by the medical imaging system 407 in any appropriate manner(e.g., as part of the remote console 411, by a stand-alone storagedevice, or any combination thereof).

The data store 414 includes a plurality of contrast media types 416 anda corresponding threshold renal function 418 for each contrast mediatype 416. Herein, a “contrast media type” may be defined at least inpart by the concentration of one or more constituents (e.g., activeingredients) of the contrast media. As another example, a “contrastmedia type” may be defined at least in part by the total amount of aparticular constituent (e.g., active ingredient) found within the totalvolume of contrast media in the syringe or found within a predefinedreference volume of contrast media in the syringe (e.g., “x” mg ofiodine per 1 ml of contrast media). Yet another example of a “contrastmedia type” may refer to the commercial names/identities for contrastmedia, each of which corresponds with desired data (e.g., threshold(e.g., minimum acceptable) renal function for a proposed receiptthereof, which may or may not be associated with certain concentrationand/or volume restrictions/guidelines for approved dosing).

The threshold renal function 418 may be of any appropriate type so longas it is indicative of patient renal function (e.g., GFR, serumcreatinine measurement). For instance, the threshold renal function 418may be in terms of a threshold GRF or an acceptable range of GFR. Asanother example, the threshold renal function 418 may be in terms of athreshold serum creatinine level or an acceptable range of serumcreatinine. The threshold renal function 418 may be expressed in anyappropriate manner (e.g., in the form of a baseline number, such that apatient renal function must be at least as great as the baseline numberor, in another embodiment, no greater than the baseline number; in theform of a range, such that patient renal function data must be withinthis range). The threshold renal function 418 may be characterized as aminimum patient renal function required/suggested for safeadministration of the corresponding contrast media to the patient 424,may be characterized as a range of acceptable patient renal functionsrequired/suggested for safe administration of the corresponding contrastmedia to the patient 424, or both.

With regard to the data store 414: 1) any way of identifying thecontrast media type 416 may be utilized; 2) any way of expressing orcharacterizing a threshold renal function 418 may be utilized (e.g., abaseline number; a range); and 3) any way of associating a givencontrast media type 416 with a threshold renal function 418 may beutilized. Although each contrast media type 416 could have a differentthreshold renal function 418, two or more of the contrast media types416 could have the same threshold renal function 418.

A given contrast media type 416 and its corresponding threshold renalfunction 418 may be characterized as defining a record 419 within thedata store 414 (e.g., a lookup table configuration). Although only threerecords 419 are illustrated for the data store 414 in FIG. 11, anyappropriate number of records 419 may be contained within the data store414. Moreover, data may be stored in any appropriate manner within thedata store 414 (e.g., in the form of a relational database, wherein agiven threshold renal function 419 may be stored in relation to multiplecontrast media types 416). Further, this data store 414 may be locatedin any appropriate location throughout a healthcare facility including,but not limited to: 1) within the injector system 430; 2) within theimaging system 407; 3) within a stand-alone information storage system;4) within a hospital information system (HIS); within a radiologyinformation system (RIS); or 5) within a picture archive andcommunication system (PACS).

The patient renal function data source 438 may be characterized as beingpart of, operatively connected with or connectable to, and/orcommunicable with the contrast media injector system 430 and/or themedical imaging system 407. Each of the contrast media injector system430 and the medical imaging system 407 could have a dedicated patientrenal function data source 438, or the contrast media injector system430 and the medical imaging system 407 could communicate with the samepatient renal function data source 438. It may also be that only one ofthe contrast media injector system 430 and the medical imaging system407 communicates with a patient renal function data source.

The patient renal function data source 438 may include data of anyappropriate type on the renal function of a patient that is to be imagedusing the contrast media injector system 430 and the imaging system 407.Patient renal function data within a given patient renal function datasource 438 may be of any appropriate type so long as the data isindicative of patient renal function (e.g., GFR, serum creatininemeasurement). For instance, patient renal function data may be expressedin terms of a GRF measurement. As another example, patient renalfunction data may be expressed in terms of a serum creatininemeasurement.

The patient renal function data source 438 may be in the form of userinput provided to the contrast media injector system 430 through theuser input device 436 for the power injector 432, through the user inputdevice 408 for the remote console 404, through a data or user inputdevice for the imaging system 407, or otherwise. The patient renalfunction data source 438 could also be in the form of a hospitalinformation system (HIS), a radiology information system (RIS), apicture archive and communication system (PACS), a renal functiontesting module (e.g., a representative device of this type beingdescribed in U.S. Patent Application Publication No. 2006/0074294 toWilliams et at, published Apr. 6, 2006), or the like. A given patientrenal function data source 438 may include any one or more of theforegoing. Patient renal function data from any of these “external”components may communicate with the contrast media injector system 430and/or the imaging system 407 in any appropriate manner to make patientrenal function information available to the contrast media injectorsystem 430 and/or the imaging system 407 (e.g., the patient renalfunction data source 438 need not be input to the contrast mediainjector system 430 through the user input device 436 of the powerinjector 432).

One embodiment of a control module is illustrated in FIG. 12, may beutilized by the injector system 430 and/or the imaging system 407, andis identified by reference numeral 440. The control module 440 may beutilized in relation to the power injector 432 and/or the imaging device422 shown in FIG. 11. All or any portion of the control module 440 maybe incorporated by the remote console 404 of the contrast media injectorsystem 430, by the power injector 432, by the remote console 409 of theimaging system 407, by the imaging device 422, or by any combinationthereof. Generally, the control module 440 includes a renal functionassessment module 442. This renal function assessment module 442 mayinclude one or more processors 444. The processor(s) 444 of the renalfunction assessment module 442 may be programmed or otherwise configuredin accordance with at least one of prompt logic 446 and comparativelogic 448 (e.g., programmed to execute the protocols 450 and 480 thatare addressed below). Generally, the prompt logic 446 may be used by thecontrast media injector system 430 and/or the imaging system 407 toissue (e.g., visually display) a prompt for a user to manually inputrenal function information for the patient 424 to the contrast mediainjector system 430 and/or imaging system 407, and the comparative logic448 may be used by the contrast media injector system 430 and/or imagingsystem 407 to assess the renal function of the patient 424 to determinewhether or not an injection for this patient 424 should proceed (e.g.,whether the power injector 432 should allow itself to be operated so asto provide a contrast media discharge). In the case where the imagingsystem 407 is operatively connected with the injector system 430, orwhere the imaging system 407 and the injector system 430 share a commonremote console, the prompt logic 446 may be used by the injector system430 and/or the imaging system 407 to issue (e.g., visually display) aprompt for a user to manually input renal function information for thepatient 424 to the injector system 430 and/or the imaging system 407,and the comparative logic 448 may be used by the injector system 430and/or imaging system 407 to assess the renal function of the patient424 to determine whether or not an injection should proceed in relationto this patient 424.

One embodiment of a protocol that may be used by the prompt logic 446 ofthe renal function assessment module 442 (FIG. 12) is shown in FIG. 13and is identified by reference numeral 450. Generally, the protocol 450is directed to issuing a prompt (e.g., a message on at least one of thedisplays 406, 411, 434) for a user to manually input renal functioninformation for the patient 424 to be imaged. Step 452 of the protocol450 is directed to issuing a prompt for the entry of patient realfunction information (e.g., data that is representative of or thatotherwise relates to the renal function of the patient 424). This promptmay be presented on the injector system's remote console display 406, onthe power injector display 434, on a display (not shown) of the imagingdevice 422, on the imaging system's remote console display 411, on adisplay of a single, commonly shared remote console, or any combinationthereof, and may be presented in any appropriate manner (e.g., in theform of a message or request for entry of the noted information).

Different types of prompts are embodied by step 452. The prompt of step452 may be a request for user input of patient renal function data(e.g., any data that is representative of the renal function of thepatient 424), and as noted by step 454 of the prompt protocol 450 ofFIG. 13. User input for purposes of step 456 may be provided (e.g.,manually input) through a user input device 408 of the remote console404, through a user input device 436 of the power injector 432, througha data or user input device (not shown) of the imaging device 422,through a user input device 413 of the remote console 409 that isassociated with the imaging device 422 and that is located in thecontrol room 402, or any combination thereof. If patient renal functiondata is entered, step 456 allows the protocol 450 to proceed to step458, which is directed to comparing this user input to threshold renalfunction data (e.g., through execution of a protocol 480 that isillustrated in FIG. 14 and that will be addressed in more detail below).Otherwise, the protocol 450 instead proceeds from step 456 to step 460,which will also be addressed in more detail below.

Another form for the prompt associated with step 452 of the protocol 450of FIG. 13 is addressed by step 468. The prompt may be in the form of arequest for confirmation that a user/operator of the contrast mediainjector system 430 and/or or imaging system 407 has determined that therenal function of the patient 424 is acceptable for proceeding with aninjection of a certain contrast media (step 468). User input forpurposes of step 468 may be provided (e.g., manually input) through theuser input device 408 of the injector system's remote console 404,through a user input device 436 of the power injector 432, through adata or user input device (not shown) of the imaging device 422, througha user input device 413 of the imaging system's remote console 409,through a user input device (not shown) of a single, commonly sharedremote console, or any combination thereof. If the renal functionassessment module 442 receives positive confirmation that the renalfunction of the patient 424 is acceptable to proceed with an injectionof contrast media (step 470), the protocol 450 proceeds to step 472.Otherwise, the protocol 450 proceeds from step 470 to step 460.

Step 460 of the protocol 450 of FIG. 13 is reached when a patient renalfunction check has failed in at least some respect. For example, step460 may be reached as a result of the user failing to enter thepatient's renal function data (e.g., for purposes of step 456). Asanother example, step 460 may be reached as a result of the user failingto input a required confirmation that the patient's renal function datahas been checked and/or meets or exceeds a particular minimum renalfunction requirement from step 470. Because of this renal function checkfailure, the proposed injection of the patient 424 by the contrast mediainjector system 430 is not allowed to proceed, which is shown in step460 of the protocol 450. This injection prohibition of step 460 may beimplemented in any appropriate manner. For instance, it may beimplemented by activating a lock-out function incorporated by thecontrast media injector system 430, by not allowing the contrast mediainjector system 430 to “arm” or to be “enabled” to run a programmedinjection protocol, by not allowing a user/operator to initiate (e.g.,“run” or “start”) a programmed injection protocol, by not allowing auser/operator to inject contrast media into the patient 424 manually(e.g., using one or more hand controls (e.g., buttons, levers) of thecontrast media injector system 430, or any combination thereof.

One or more additional functionalities may be employed in response tothe failure of a renal function check. Step 462 of the protocol 450 isdirected to issuing one or more alarms. Each alarm may be of anyappropriate type (e.g., audible, visual). Step 464 is directed togenerating next action instructions. These instructions could bepresented on the injector system's remote console display 406, on thepower injector display 434, on a display (not shown) of the imagingdevice 422, on the imaging system's remote console display 411, on adisplay of a single, commonly shared remote console, or any combinationthereof. These instructions could be programmed into the contrast mediainjector system 430 and/or the medical imaging system 407, and couldprovide guidance to an operator as to how to deal with the failure of arenal function check. Any one or more of steps 460, 462, and 464 couldbe executed in response to the failure of a renal function check and inany appropriate order, including where two or more of these steps areexecuted simultaneously.

One embodiment of a protocol that may be used by the comparative logic448 of the renal function assessment module 442 (FIG. 12) is shown inFIG. 14 and is identified by reference numeral 480. Generally, theprotocol 480 is directed to assessing the renal function of the patient424 to determine whether or not an injection should proceed (e.g.,whether the contrast media injector system 430 should be operated so asto provide a contrast media discharge). Step 482 of the protocol 480 isdirected to receiving or retrieving information (e.g., through at leastone of the user input devices 408, 413, 436) in the form of renalfunction data for the patient 424. This renal function data may be anytype of data that is representative of the renal function of the patient424 (e.g., information that quantifies the renal function of the patient424 in at least some respect), and may be received/retrieved in anyappropriate manner.

Threshold renal function data is received or retrieved pursuant to step484 of the protocol 480. This threshold renal function data may be anytype of data that represents a threshold for the renal function thatshould exist in order for the patient 424 to receive an injection fromthe contrast media injector system 430 (e.g., an injection of aparticular type of contrast media). The threshold renal function datamay be received/retrieved in any appropriate manner. A user could lookup the threshold renal function data from any appropriate source/sourcesand manually input the same into the contrast media injector system 430and/or imaging system 407 (e.g., through at east one of the user inputdevices 408, 413, 436). A user could search the data store 414 (e.g., bymanually entering a contrast media type 416 into the contrast mediainjector system 430 (or select the same from a listing provided by thesystem 430) through at least one of the user input devices 408, 413, 436to identify a relevant threshold renal function 418. This relevantthreshold renal function 418 could be retrieved in any appropriatemanner by the contrast media injector system 430 and/or imaging system407 pursuant to step 484 (e.g., by a user “clicking” on the thresholdrenal function 418 identified from the search of the data store 414; bythe contrast media injector system 430 and/or imaging system 407automatically retrieving the relevant threshold renal function 418 fromthe information provided by the user on the contrast media type 416).

Yet another option for purposes of step 484 of the protocol 480 of FIG.14 would be for the contrast media injector system 430 and/or imagingsystem 407 to automatically retrieve the threshold renal function datafor step 484, for instance, by the contrast media injector system 430reading a data tag or the like on a syringe installed on the powerinjector 432 (e.g., by the power injector 432 incorporating anappropriate electromagnetic device and by such a syringe including anRF/RFID tag (more generally, a data storage device of any appropriatetype) that at least identifies the contrast media type 416 within thesyringe (e.g., including a volume of fluid within the syringe and/or aconcentration of one or more constituents of the contrast media), all inaccordance with the discussion presented above regarding the embodimentof FIG. 6). The threshold renal function data could be stored on such adata tag on the syringe, and then read by the electromagnetic device ofthe power injector 432 (more generally, a “reader”) for purposes of step484. The threshold renal function data could also be retrieved bystoring the contrast media type 416 on such a data tag on the syringe,which could then be read by the electromagnetic device of the powerinjector 432 for purposes of step 484. The identification of thecontrast media type 416 within the syringe could then be used to searchthe data store 414 to identify the corresponding threshold renalfunction 418 for purposes of step 484 of the protocol 480.

The patient renal function data (step 482) is compared with thethreshold renal function data (step 484) pursuant to step 486 of theprotocol 480. This comparison may be undertaken in any appropriatemanner (e.g., by one or more processors 444 of the renal functionassessment module 442 of FIG. 12). Step 488 of the comparative renalfunction protocol 480 of FIG. 14 is directed to determining if thepatient renal function data (step 482) complies with the threshold renalfunction data (step 484). For instance, a determination may be made asto whether the patient renal function data (step 482) meets or exceedsthe threshold renal function data (step 484). In any case, if thepatient renal function data (step 482) complies with the threshold renalfunction data (step 484), the protocol 480 proceeds to step 490, whichis directed to allowing the injection of the patient 424 by the contrastmedia injector system 430 to proceed. If the patient renal function data(step 482) does not comply with the threshold renal function data (step484), the protocol 480 instead proceeds to step 492.

Step 492 of the protocol 480 of FIG. 14 is reached when a renal functioncheck has failed in at least some respect. In this regard, the injectionof the patient 424 by the contrast media injector system 430 is notallowed to proceed through execution of step 492 of the protocol 480.This may be implemented in any appropriate manner, for instance inaccordance with step 460 of the prompt protocol 450 discussed above inrelation to FIG. 13.

One or more additional functionalities may be employed in response tothe failure of a renal function check. Step 494 of the protocol 480 isdirected to issuing one or more alarms. Each alarm may be of anyappropriate type (e.g., audible, visual). Step 496 is directed togenerating next action instructions. These instructions could bepresented on the injector system's remote console display 406, on thepower injector display 434, on a display (not shown) of the imagingdevice 422, on the imaging system's remote console display 411, on adisplay of a single, commonly shared remote console, or any combinationthereof. These instructions could be programmed into the contrast mediainjector system 430 and/or the medical imaging system 407, and couldprovide guidance to an operator as to how to deal with the failure of arenal function check. Any one or more of steps 492, 494, and 496 couldbe executed in response to the failure of a renal function check and inany appropriate order, including where two or more of these steps areexecuted simultaneously.

One embodiment of a contrast media storage/dispensing unit isillustrated in FIG. 15 and is identified by reference numeral 500. Thecontrast media storage/dispensing unit 500 may be utilized inconjunction with the imaging suite 400 discussed above in relation toFIGS. 11-14. However, the contrast media storage/dispensing unit 500 mayalso be implemented independently of such an imaging suite 400.Generally, the contrast media storage/dispensing unit 500 is directed toproviding a renal function check prior to releasing contrast media foruse in conjunction with an injection of a patient (e.g., prior toproviding contrast media to a technician for use in a proposed injectionprocedure for a given patient).

The contrast media storage/dispensing unit 500 may be characterized asincluding or being in the form of a supply 502 of discrete quantities ofcontrast media. These discrete quantities of contrast media may beretained within a plurality of contrast media containers 504 that are ofany appropriate type (e.g., syringes, vials, bags), that collectivelydefine the contrast media supply 502, and that may be stored in anyappropriate manner by/within the contrast media storage/dispensing unit500. Multiple containers 504 of one or more contrast media types may beincluded within the contrast media supply 502. In one embodiment, atleast some of the contrast media containers 504 being stored within thecontrast media storage/dispensing unit 500 are in the form of a“prefilled syringe.” “Prefilled syringes” are syringes that are loadedwith contrast media or other medical fluids at a manufacturing facilityprior to transporting the same to an end-use facility such as ahospital, clinic, or the like. Although all of the contrast mediacontainers 504 being stored within the contrast media storage/dispensingunit 500 may be of a common type and/or may be of a commonsize/configuration, such may not be the case in all instances.

The contrast media containers 504 are in a sealed condition or stateboth when stored in the contrast media storage/dispensing unit 500, aswell as when/after being released from the contrast mediastorage/dispensing unit 500. Being in a “sealed condition” encompassesthat a given contrast media container 504 is not currently in aconfiguration to inject contrast media into a patient 424. Being in a“sealed condition” also encompasses that a given contrast mediacontainer 504 is usable in a patient injection procedure only afterbeing released from the contrast media storage/dispensing unit 500. Eachof the contrast media containers 504 may be characterized as beingadapted for use with a medical fluid delivery system, such as thecontrast media injector system 430. After being released from thecontrast media storage/dispensing unit 500, a given contrast mediacontainer 504 may need to be appropriately interconnected with a medicalfluid delivery system (e.g., contrast media injector system 430) priorto being able to inject contrast media into a patient 424.

Each of the contrast media containers 504 may include a data storagedevice 514 of any appropriate type (e.g., an RF or RFID tag). Anyappropriate information may be stored on the data storage device 514 ofeach contrast media container 504. Representative data that may bestored on a given data storage device 514 includes without limitation acontrast media type identifier (where a “contrast media type” may: 1) bedefined at least in part by the concentration of one or moreconstituents (e.g., active ingredients) of the contrast media; 2) bedefined at least in part by the total amount of a particular constituent(e.g., active ingredient) found within the total volume of contrastmedia in the corresponding container 504 or found within a predefinedreference volume of contrast media in the corresponding container 504(e.g., “x” mg of iodine per 1 ml of contrast media); 3) refer to thecommercial names/identities for contrast media), threshold renalfunction data (e.g., threshold (e.g., minimum acceptable) renalfunction, which may or may not be associated with certain concentrationand/or volume restrictions/guidelines for approved dosing), and thelike.

Other components of the contrast media storage/dispensing unit 500include a renal function assessment module 510 (e.g., at least generallyin accordance with the renal function assessment module 442 of thecontrol module 440 of FIG. 12, and thereby including one or moreprocessors that may be programmed to undertake the protocols 520 and 540that are addressed below) and at least one data or user input device 508(in accordance with the user input devices 408, 413, 436 discussed abovein relation to the imaging suite 400 of FIG. 11). The contrast mediastorage/dispensing unit 500 may also include one or more displays 506,as well as the data store 414 discussed above in relation to the imagingsuite 400 of FIG. 11. Renal function information may also be madeavailable to the contrast media storage/dispensing unit 500 (e.g., tothe renal function assessment module 510) through a renal function datasource 512 (e.g., HIS, RIS, PACS, injector system 430, imaging system407, or a patient electronic medical records system).

FIG. 16 illustrates one embodiment of a release protocol 520 that may beincorporated by the renal function assessment module 510 for thecontrast media storage/dispensing unit 500 for purposes of determiningwhether a contrast media container 504 should be released/dispensed bycontrast media storage/dispensing unit 500. Step 522 of the protocol 520is directed to inputting (entering or selecting) or acquiring thecontrast media type (e.g., which may include one or more of brand name,active ingredient, concentration, and volume) that is desired to beretrieved from the contrast media storage/dispensing unit 500. The inputassociated with step 522 may be provided in any appropriate manner, suchas through the user input device 508 of the contrast mediastorage/dispensing unit 500.

Step 524 of the release protocol 520 of FIG. 16 is directed toquestioning/inquiring whether the patient renal function has beendetermined to be compatible with the contrast media type that was inputpursuant to step 522. This may be presented on the display 506 of thecontrast media storage/dispensing unit 500. User input may be providedthrough step 526 of the protocol 520 (e.g., through the user inputdevice 508). If the user input was an affirmative response (e.g., a“yes”), the protocol 520 proceeds from step 528 to step 530. Step 530 isdirected to releasing a contrast media container 504 from the contrastmedia supply 502 in accordance with the contrast media type identifiedthrough step 522. If no user input is provided pursuant to step 526, orif the user input was a negative response (e.g., a “no”), the contrastmedia storage/dispensing unit 500 will not release a contrast mediacontainer 504 from the contrast media supply 502 (e.g., pursuant to step532 of the release protocol 520).

One or more additional functionalities may be employed in response tothe contrast media release/dispensing denial of step 532. For example,next action instructions may be generated. These instructions could bepresented on the storage/dispensing unit's display 506. Theseinstructions could be programmed into the contrast mediastorage/dispensing unit 500, and could provide guidance to a technicianas to how to deal with the failure of a renal function check.

FIG. 17 illustrates another embodiment of a release protocol 540 thatmay be incorporated by the renal function assessment module 510 for thecontrast media storage/dispensing unit 500 for purposes of determiningwhether a contrast media container 504 should be released/dispensed bycontrast media storage/dispensing unit 500. Step 542 of the protocol 540is directed to inputting or acquiring the contrast media type that isdesired to be retrieved from the contrast media storage/dispensing unit500. The input associated with step 542 may be provided in anyappropriate manner, such as through the user input device 508 of thecontrast media storage/dispensing unit 500.

Step 544 of the release protocol 540 of FIG. 17 is directed to providinginput to the contrast media storage/dispensing unit 500 regardingpatient renal function data of the above-described type. This may beundertaken in any appropriate manner. One option is for patient renalfunction data (e.g., GFR, serum creatinine measurement) to be manuallyinput by a user through the user input device 508 of the contrast mediastorage/dispensing unit 500. Another option would be for the contrastmedia storage/dispensing unit 500 to including a listing of renalfunction data, and for a user to manually select the relevant patientrenal function data from such a listing through the user input device508. Yet another option could be for the contrast mediastorage/dispensing unit 500 to be operatively connected with (e.g., incommunication with) one or more renal function data sources 512 (e.g.,HIS, RIS, PACS, injector system 430, imaging system 407, a patientelectronic medical records system), and to retrieve the patient renalfunction data for step 544 from such a renal function data source 512.For instance, a user could input an appropriate patient identifier tothe contrast media storage/dispensing unit 500 through the user inputdevice 508, and the contrast media storage/dispensing unit 500 couldthen retrieve the patient renal function data for step 544 from one ormore renal function data sources 512. As an alternative to a usermanually entering the patient renal function data, that data could beretrieved from a renal function data source 512 by the unit 500 inresponse to an electronic read device (not shown) of the unit 500identifying the patient by way of reading an appropriate data source(e.g., bar code or RFID tag presented to the unit 500 by a technician).In other embodiments, the patient's renal function data could be storedon an appropriate data source (e.g., bar code or RFID tag) and could beinput into the unit 500 simply by a technician exposing that data sourceto an electronic read device (not shown) of the unit 500.

Threshold renal function data is retrieved pursuant to step 546 of therelease protocol 540 of FIG. 17. This threshold renal function data maybe any type of data that represents a threshold for the renal functionthat should exist in order for the patient to receive an injection of aparticular type of contrast media (e.g., from the contrast mediainjector system 430). The threshold renal function data may be retrievedin any appropriate manner. A user could look up the threshold renalfunction data from any appropriate source/sources and manually input thesame into the contrast media storage/dispensing unit 500 (e.g., throughthe user input device 508). A user could search the data store 414(e.g., by manually entering a contrast media type into the contrastmedia storage/dispensing unit 500 through the user input device 508) toidentify a relevant threshold renal function 418 (e.g., see FIG. 11regarding the data store 414). This relevant threshold renal function418 could be retrieved in any appropriate manner by the contrast mediastorage/dispensing unit 500 pursuant to step 546 (e.g., by a user“clicking” on the threshold renal function 418 identified from thesearch of the data store 414; by the contrast media storage/dispensingunit 500 automatically retrieving the relevant threshold renal function418 from the information provided by the user on the contrast media type416—utilizing the data store 414).

Step 548 of the release protocol 540 is directed to determining if thepatient renal function data (step 544) complies with the threshold renalfunction data (step 546). This determination/comparison may beundertaken in any appropriate manner (e.g., by one or more processors ofthe renal function assessment module 510). For instance, a determinationmay be made as to whether the patient renal function data (step 544)meets or exceeds the threshold renal function data (step 546). In anycase, if the patient renal function data (step 544) complies with thethreshold renal function data (step 546), the protocol 540 proceeds tostep 550, and which is directed to releasing a contrast media container504 from the contrast media supply 502 in accordance with the contrastmedia type provided through step 542. If the patient renal function data(step 544) does not comply with the threshold renal function data (step546), the contrast media storage/dispensing unit 500 will not release acontrast media container 504 from the contrast media supply 502 (e.g.,pursuant to step 552 of the release protocol 540).

Any of the modules, protocols, logic, or the like addressed in relationto the renal function checks for the embodiments of FIGS. 11-17 may beimplemented in any appropriate manner, including without limitation inany appropriate software, firmware, or hardware, using one or moreplatforms, using one or more processors, using memory of any appropriatetype, using any single computer of any appropriate type or a multiplecomputers of any appropriate type and interconnected in any appropriatemanner, or any combination thereof. These modules, protocols, logic, orthe like may be implemented at any single location or at multiplelocations that are interconnected in any appropriate manner (e.g., viaany type of network).

One embodiment of a medical system is illustrated in FIG. 18A and isidentified by reference numeral 600. The medical system 600 includes acontrast media injector system 602, an injection data management module660, an imaging system 690, a contrast media storage/dispensing unit 500(discussed above in relation to FIG. 15), a hospital information systemor HIS 700, a picture archiving and communications system or PACS 710,and a radiology/radiological information system or RIS 720.

The imaging system 690 may be in accordance with the imaging system 407discussed above in relation to FIG. 11. In this regard, the imagingsystem 690 may include an imaging device or unit 692, as well as aremote console (not shown in FIG. 18A). The imaging device 692 mayutilize any appropriate imaging technology or combination of imagingtechnologies.

The HIS 700 may be characterized as a computer system that is configuredto manage information that relates to one or more aspects of hospitaloperations. This computer system may utilize any appropriatearchitecture or combination of architectures. The HIS 700 may utilizeany appropriate combination of hardware and/or software that isdistributed in any appropriate arrangement and that is operativelyinterconnected in any appropriate manner (e.g., any appropriatecommunication link or combination of communication links, includingutilizing one or more networks of any appropriate type). The HIS 700 mayutilize one or more servers, one or more processors integrated in anyappropriate processing architecture, one or more workstations (e.g.,desktop computers; laptop computers; terminals in the form of a displayand keyboard), or the like that are in communication over one or morenetworks of any appropriate type (e.g., a local area network; a widearea network; the Internet; a private network).

A data storage system of any appropriate type may be used by the HIS 700to store data that relates to one or more aspects of hospital operations(e.g., any appropriate data storage architecture of computer-readablestorage medium). Any appropriate data structure or combination of datastructures may be utilized by the HIS 700. Representative data that maybe stored by the HIS 700 includes medical/patient information (e.g.,electronic patient medical records), administrative information, andfinancial information. Data may be stored by the HIS 700 on acomputer-readable storage medium and in any appropriate form. Data maybe stored in one or more databases of the HIS 700, and data stored bythe HIS 700 may be linked as desired/required and in any appropriatemanner.

The HIS 700 may be characterized as including the one or moresubsystems, along with their corresponding data. Representativesubsystems of the HIS 700 may include without limitation PACS 710; RIS720; a Clinical Information System (CIS); a Laboratory InformationSystem (LIS); a Pharmacy Information System (PIS); a Nursing InformationSystem (NIS); and a Financial Information System (FIS).

The PACS 710 may be characterized as a computer system (e.g.,combination of hardware and software) that provides for storage,retrieval, management, access to, presentation, and distribution ofmedical images of any appropriate type (e.g., magnetic resonance,computed tomography, ultrasound, positron emission tomography, etc).Image files may be stored by the PACS 710 on any appropriatecomputer-readable storage medium (e.g., in the form of one or moredigital files). Non-image data may be stored by the PACS 710.

The PACS 710 may utilize one or more servers that each have one or moreimage databases, and that may be accessed in any appropriate manner(e.g., through a local area network, through a wide area network, overthe Internet or any other public network). The above-noted imagingsystem 690 may be characterized as being part of the PACS 710. Othercomponents of the PACS 710 may include without limitation a network fordistribution and exchange of patient information, one or moreworkstations (e.g., a terminal and keyboard; a desktop computer; alaptop computer), and a data storage system (e.g., computer readablestorage medium) for the storage and retrieval of images and relateddocumentation.

The RIS 720 may be characterized as a computer system (e.g., combinationof hardware and software) that provides for storage, review,manipulation, and distribution of patient radiological data and imagery.Patient radiological data and imagery may be stored by the RIS 720 onany appropriate data storage system (e.g., computer-readable storagemedium). The RIS 720 may incorporate patient management functionality(e.g., tracking patient workflow within a radiology department; storing,retrieving, and viewing image data and related documentation),scheduling functionality, patient tracking functionality (e.g.,providing access to the entirety of a patient's radiology history),reporting functionality, image tracking functionality, and billingfunctionality (e.g., financial recordkeeping, electronic payment, claimsubmission).

The contrast media injector system 602 may be in the form of a powerinjector (e.g., power injector 210 discussed above in relation to FIG.1A; power injector 240 discussed above in relation to FIGS. 1B-D; powerinjector 10 discussed above in relation to FIGS. 2A-5B; contrast mediainjector system 430 discussed above in relation to FIG. 11). Inaccordance with the foregoing embodiments, the contrast media injectorsystem 602 includes a powerhead 604 and what is commonly referred to asa remote console 650 (more generally a first console 650). In oneembodiment, the powerhead 604 is located in one location (e.g., imagingroom 420 in FIG. 11), while the remote console 650 is located in anotherlocation (e.g., control room 402 in FIG. 11). However, the powerhead 604and remote console 650 could be co-located (e.g., within an imaging room420, shown in FIG. 11).

The remote console 650 may include at least one display 652, at leastone user or data input device 654, and possibly a processing system 656(e.g., a CPU; one or more processors). The discussion presented abovewith regard to the remote console 404 of the contrast media injectorsystem 430 of FIG. 11 is equally applicable to the remote console 650used by the medical system 600 of FIG. 18A. The remote console 650 maybe a designated part of the contrast media injector system 602, and maybe configured to only communicate with at least one other portion of thecontrast media injector system 602 (e.g., the powerhead 604, forinstance through the injection data management module 660 (e.g., whichmay be incorporated at least in part by a powerpack). Another option isfor the remote console 650 to be a designated part of the contrast mediainjector system 602, but where it may be configured to communicate withboth the imaging system 690 and at least one other portion of thecontrast media injector system 602 (e.g., the powerhead 604, forinstance through the injection data management module 660). Yet anotheroption is for the remote console 650 to be a shared unit between thecontrast media injector system 602 and the imaging system 690. Theremote console 650 could be a designated part of the imaging system 690,but where it may be configured to communicate with both the imagingdevice 692 and the contrast media injector system 602 (e.g., thepowerhead 604, for instance through the injection data management module660).

The contrast media injector system 602 of FIG. 18A includes or at leastutilizes the injection data management module 660. As will be discussedin more detail below, the injection data management module 660 may beconfigured to convert data from at least one format into at least oneother format. Generally, the injection data management module 660provides for or accommodates communication between the contrast mediainjector system 602 and various other components of the medical system600 (which may be referred to as sub-systems of the medical system 600).Any architecture may be used for these handling these communications. Inthe illustrated embodiment, the injection data management module 660 isnot part of the powerhead 604, but is able to communicate with thepowerhead 604 over a communication link 672 of any appropriate type(e.g., a wired connection; an appropriate data cable; wirelessly). Theremote console 650 may communicate with the powerhead 604 over acommunication link 670 of any appropriate type (e.g., a wiredconnection; an appropriate data cable; wirelessly), for instance throughthe injection data management module 660 (a conversion of a data formatfor data transmitted between the powerhead 604 and the remote console650 may not be required). Communications between the remote console 650and the powerhead 604 may utilize a first CAN-compliant format (whereCAN stands for “Controller Area Network”). In one embodiment, data istransmitted over the communication link 670 is in accordance with a CAN2.0A standard.

The contrast media injector system 602 may communicate with the imagingsystem 690 over a communication link 678 of any appropriate type (e.g.,a wired connection; an appropriate data cable; wirelessly).Communications between the contrast media injector system 602 and theimaging system 690 may be directed through the injection data managementmodule 660. The contrast media injector system 602 may utilize oneCAN-compliant format (e.g., CAN 2.0A), while the imaging system 690 mayutilize another CAN-compliant format (e.g., CiA 425). Contrastadministration data from the contrast media injector system 602 may beconverted from one format to another format by the injection datamanagement module 660 for transmission to the imaging system 690. In oneembodiment, the medical system 600 is configured such that there may betwo-way communications between the contrast media injector system 602and the imaging system 690 through the injection data management module660 (e.g., such that the injection data management module 660 canprovide both a CAN 2.0A to CiA 425 conversion, as well as a CIA 425 toCAN 2.0A conversion). However, the medical system 600 could beconfigured such that there may only be one-way communications betweenthe contrast media injector system 602 and the imaging system 690 (ineither direction).

The contrast media injector system 602 may communicate with the HIS 700over a communication link 674 of any appropriate type (e.g., a wiredconnection; an appropriate data cable; wirelessly). Communicationsbetween the contrast media injector system 602 and the HIS 700 may bedirected through the injection data management module 660. The contrastmedia injector system 602 may utilize one CAN-compliant format (e.g.,CAN 2.0A), while the HIS 700 may utilize an HL-7-compliant format.Contrast administration data from the contrast media injector system 602may be converted from one format to another format by the injection datamanagement module 660 for transmission to the HIS 700 (e.g., CAN 2.0A toHL-7). In one embodiment, the medical system 600 is configured such thatthere is only one-way communication between the powerhead 604 ofcontrast media injector system 602 and the HIS 700 (e.g., from thepowerhead 604 to the HIS 700, through the injection data managementmodule 660).

The contrast media injector system 602 may communicate with the contrastmedia storage/dispensing unit 500 (e.g., CMSDU 500) over a communicationlink 676 of any appropriate type (e.g., a wired connection; anappropriate data cable; wirelessly). Communications between the contrastmedia injector system 602 and the contrast media storage/dispensing unit500 may be directed through the injection data management module 660.The contrast media injector system 602 may utilize one CAN-compliantformat (e.g., CAN 2.0A), while the contrast media storage/dispensingunit 500 may utilize an HL-7-compliant format. Contrast administrationdata from the contrast media injector system 602 may be converted fromone format to another format by the injection data management module 660for transmission to the contrast media storage/dispensing unit 500(e.g., CAN 2.0A to HL-7).

The contrast media injector system 602 may communicate with the PACS 710over a communication link 680 of any appropriate type (e.g., a wiredconnection; an appropriate data cable; wirelessly). Communicationsbetween the contrast media injector system 602 and the PACS 710 may bedirected through the injection data management module 660 (e.g., FIGS.19 and 20). The communication link 680 may extend from the injectiondata management module 660 to the PACS 710 (e.g., the communication link680 need not extend through the remote console 650). The contrast mediainjector system 602 may utilize one CAN-compliant format (e.g., CAN2.0A), while PACS 710 may utilize a DICOM (“Digital imaging andCommunications in Medicine”) format. Contrast administration data fromthe contrast media injector system 602 may be converted from one formatto another format by the injection data management module 660 fortransmission to the PACS 710 (e.g., CAN 2.0A to DICOM).

The contrast media injector system 602 may communicate with the RIS 720over a communication link 682 of any appropriate type (e.g., a wiredconnection; an appropriate data cable; wirelessly). Communicationsbetween the contrast media injector system 602 and the RIS 720 may bedirected through the injection data management module 660 (e.g., FIGS.19 and 20). The communication link 682 may extend from the injectiondata management module 660 to the RIS 720 (e.g., the communication link682 need not extend through the remote console 650). The contrast mediainjector system 602 may utilize one CAN-compliant format (e.g., CAN2.0A), while the RIS 720 may utilize an HL-7-compliant format. Contrastadministration data from the contrast media injector system 602 may beconverted from one format to another format by the injection datamanagement module 660 for transmission to the RIS 720 (e.g., CAN 2.0A toHL-7).

The medical system 600 accommodates other communications. As shown inFIG. 18A, the contrast media storage/dispensing unit 500 may communicatewith the HIS 700 over a communication link 688 of any appropriate type(e.g., a wired connection; an appropriate data cable; wirelessly).Communications between the contrast media storage/dispensing unit 500and the HIS 700 may utilize an HL-7-compliant format. The medical system600 may include one or more workstations 730 (e.g., a desktop computer,a laptop). In the illustrated embodiment, a workstation 730 is able tocommunicate with the RIS 720 over a communication link 684 of anyappropriate type (e.g., a wired connection; an appropriate data cable;wirelessly), and is also able to communicate with the HIS 700 over acommunication link 686 of any appropriate type (e.g., a wiredconnection; an appropriate data cable; wirelessly).

As noted, the communication architecture between the injection datamanagement module 660 and the various sub-systems of the medical system600 (more generally the communication architecture of the medical system600) may be of any appropriate configuration. The injection datamanagement module 660 could directly communicate with one or more ofthese sub-systems (e.g., HIS 700; PACS 710; RIS 720; CMSDU 500), theinjection data management module 660 could indirectly communicate withone or more of these sub-systems, or both. For instance, thecommunication architecture could be such that data in one format (e.g.,HL-7) could be directed from the injection data management module 660 toone of these sub-systems (e.g., HIS 700), and this sub-system could thendirect this data to other subsystems that require data of the sameformat (e.g., the communication architecture could provide for anindirect communication between the injection data management module 660and one or more sub-systems of the medical system 600).

The injection data management module 660 used by or associated with thecontrast media injector system 602 may be characterized as providing acommunication interface between at least part of the contrast mediainjector system 602 (e.g., its powerhead 604) and at least one othermedical system, where this medical system(s) requires that data betransmitted from the injection data management module 660 in somethingother than a CAN-compliant format (e.g., HL-7-compliant data). FIG. 18Bpresents a schematic of one embodiment of the injection data managementmodule 660 from the medical system 600 of FIG. 18A, and that isidentified by reference numeral 660 a. The injection data managementmodule 660 a may be implemented in any appropriate architecture (e.g.,the injection data management module 660 a could be an autonomous unitin relation to the remainder of the medical system 600; one or moreparts of the injection data management system 660 a could beincorporated by one or more of the sub-systems of the medical system600). In the FIG. 18B configuration, the injection data managementmodule 660 a provides an interface between a contrast media injectorsystem 602 (e.g., its powerhead 604) and at least one medical sub-system735 that requires data to be in something other than in a CAN-compliantformat (e.g., HL-7-compliant data). Each medical sub-system 735 incommunication with the injection data management module 660 a may be ofany appropriate type, for instance the HIS 700, the RIS 720, or the PACS710 discussed above, or any other electronic medical records system(s)(e.g., a medical data or information system). The medical sub-system 735could also be in the form of the contrast media storage/dispensing unit500 described in relation to FIG. 18A.

The injection data management module 660 a may include a user interface662 of any appropriate type. This user interface 662 may include one ormore user input devices 662 a of any appropriate type (e.g., a keyboard,a touchscreen, a graphical user interface), one or more displays 662 bof any appropriate type, or both. The injection data management module660 a may use one or more data conversion modules 664, with each dataconversion module 664 converting data (e.g., received from the contrastmedia injector system 602) from one CAN-compliant format to a differentformat. At least one data conversion module 664 of the injection datamanagement module 660 a may be configured to convert data (e.g.,received from the contrast media injector system 602) from aCAN-compliant format to a non-CAN-compliant format (e.g., anHL-7-compliant format). Any data conversion function provided by theinjection data management module 660 a may utilize one or moreprocessors 620 of any appropriate type and disposed in any appropriatearchitecture.

The injection data management module 660 a may use a data processingmodule or unit 666. The data processing unit 666 and each dataconversion module 664 may be arranged in any appropriate architecture(e.g., each data conversion module 664 and the data processing unit 666could be part of a common unit; one or more data conversion modules 664may be disposed in a common unit, one or more data conversion modules664 may each be disposed in a separate unit, or both; the dataprocessing unit 666 could be disposed in a separate unit from each ofthe data conversion modules 664; the data processing unit 666 and atleast one data conversion module 664 could be disposed in a common unit,and one or more data conversion modules 664 could be disposed in one ormore separate units). One or more processors 620 may be used by the dataprocessing unit 666 in relation to: processing requests for contrastadministration data received by the injection data management module 660a from one or more medical sub-systems 735; transmitting data from theinjection data management module 660 a to one or more medicalsub-systems 735 (e.g., in response to a request for data from one ormore medical system 735; in an automated or programmed manner; otherthan in response to a request for data from one or more medical system735; at the initiation of the contrast media injector system 602 itselfand/or the injection data management module 660 a itself); storinginformation on the injection data management module 660 a (e.g., withinits data storage system 622, discussed below); or any combinationthereof. Multiple processors 620 may be arranged in any appropriateprocessing architecture for purposes of the injection data managementmodule 660 a.

Software 667 of any appropriate type/format may be used by the injectiondata management module 660 a to translate data from one format toanother, to receive input from one or more medical sub-systems 735, totransmit data to one or more medical sub-systems 735, to store data onthe injection data management module 660 a, and/or in relation to anyother functionality of the injection data management module 660 a.Updates to the software 667 may be downloaded to the injection datamanagement module 660 a through one or more communication ports 648 ofany appropriate type (e.g., the injection data management module 660 amay include a communication port 648 in the form of an Ethernet portthat would allow software updates to be downloaded to the injection datamanagement module 660 a over the Internet).

The injection data management module 660 a may utilize a data storagesystem 622 of any appropriate type (e.g., hard drive, solid statememory, flash memory, non-volatile ram, any appropriate memory). Thedata storage system 622 may be arranged in any appropriate data storagearchitecture. Generally, contrast administration data may be transmittedto the injection data management module 660 a and stored on its datastorage system 622. The contrast administration data that is provided tothe injection data management module 660 a may be of any appropriatetype (e.g., predefined) and may be provided to the injection datamanagement module 660 a on any appropriate basis (e.g., on a real-timebasis; intermittently; on a batch-type basis, for instance at the end ofa programmed injection).

The injection data management module 660 a may have its own userinterface 662 in accordance with FIG. 18B. One or more of the remoteconsole 650, one or more workstations 730, any user interfaceincorporated by or otherwise associated with the contrast media injectorsystem 602 (e.g., a keyboard or touchscreen display), and/or any otheruser interface of the medical system 600 could provide a userinterface/input function for the injection data management module 660 a.More than one user interface could be used for providing user input tothe injection data management module 660 a (e.g., a user interface 662incorporated by the injection data management module 660 a, along withone or more of the above-noted types of devices). User input to theinjection data management module 660 a could also be provided entirelythrough an external device that is operatively connected with theinjection data management module 660 a, but that is actually part ofanother sub-system 735 of the medical system 600.

Any appropriate architecture may be used by the injection datamanagement module 660 a. All of the functionality of the injection datamanagement module 660 a could be incorporated into a single physicalunit. A distributed architecture could be used for the injection datamanagement module 660 a as well. For instance, the data conversionfunctionality could be provided by one or more separate units, and thedata processing/data storage/user interface functionalities could beprovided by a separate unit that is operatively connected with one ormore data conversion units.

FIG. 19 presents a functional schematic or block diagram of oneconfiguration for at least part of the injection data management module660 for the medical system 600 of FIG. 18A, and that is identified byreference numeral 660 b in FIG. 19. Initially, the injection datamanagement module 660 b may incorporate any one or more of the featuresof the injection data management module 660 a discussed above inrelation to FIG. 18B. In accordance with the foregoing, the powerhead604 of the contrast media injector system 602 may include a display 608and at least one user input device 610 (e.g., a keyboard; configuringthe display 608 to have touch screen functionality).

The contrast media injector system 602 may utilize what may becharacterized as an injector communication bus 606 for transmitting datathroughout the contrast media injector system 602. The injectorcommunication bus 606 may utilize a first CAN-compliant format for datacommunications, such as a CAN 2.0A. Although the injector communicationbus 606 is shown as being located within the powerhead 604, the injectorcommunication bus 606 may extend throughout the contrast media injectorsystem 602. For instance, the communication link 670 between the remoteconsole 650 and the powerhead 604, as well as the communication link 672between the powerhead 604 and the injection data management module 660b, may be considered as part of the injector communication bus 606 aswell.

The injection data management module 660 b of the FIG. 19 embodiment maybe in the form of or as a component of a variation of the powerpack 246discussed above in relation to the power injector 240 of FIG. 1B (e.g.,by its inclusion of a first data conversion module 614 and a third dataconversion module 640). At least part of the injection data managementmodule 660 b may be integrated other than through the powerpack 246(e.g., part or the entirety of the injection data management module 660b could be separate from the powerpack 246). The injection datamanagement module 660 b may use any appropriate architecture. In anycase, the powerhead 604 of the contrast media injector system 602communicates with the injection data management module 660 b over thenoted communication link 672. In the illustrated embodiment, theinjection data management module 660 b includes three different dataconversion modules. Any appropriate number of data conversion modulesmay be utilized by the injection data management module 660 b.

The injection data management module 660 b includes a first dataconversion module 614 that is operatively interconnected with theinjector communication bus 606 of the contrast media injector system 602(e.g., via the communication link 672, which may actually be part of theinjector communication bus 606). Generally, the first data conversionmodule 614 converts contrast administration data from a firstCAN-compliant format (e.g., CAN 2.0A) into an HL-7-compliant format.This may be undertaken in any appropriate manner.

The first data conversion module 614 may utilize one or more processors620 of any appropriate type. One or more processors 620 may be used forthe data conversion provided by the first data conversion module 614.One or more processors 620 may be used by the injection data managementmodule 660 b to process requests for contrast administration datareceived by the injection data management module 660 b from the HIS 700.Multiple processors 620 may be arranged in any appropriate processingarchitecture for purposes of the first data conversion module 614.

The first data conversion module 614 may utilize the data storage system622 of the injection data management module 660 b, which again may be ofany appropriate type/configuration (e.g., hard drive, solid statememory, flash memory, non-volatile ram). The data storage system 622 maybe arranged in any appropriate data storage architecture. Generally,contrast administration data may be transmitted to the first dataconversion module 614 and stored on the data storage system 622 of theinjection data management module 660 b. The contrast administration datathat is provided to the first data conversion module 614 may be of anyappropriate type (e.g., predefined) and may be provided to the firstdata conversion module 614 on any appropriate basis (e.g., on areal-time basis; intermittently; on a batch-type basis, for instance atthe end of a programmed injection).

The injection data management module 660 b may be characterized asincluding a first communication port 624, a CMSDU communication port628, and a RIS communication port 629. The first communication port 624of the injection data management module 660 b is operativelyinterconnected with the HIS 700 through the communication link 674. TheCMSDU communication port 628 of the injection data management module 660b is operatively interconnected with the contrast mediastorage/dispensing unit 500 through the communication link 676. The RIScommunication port 629 of the injection data management module 660 b isoperatively interconnected with the RIS 720 through the communicationlink 682. The injection data management module 660 b could have a singlecommunication port for outputting data in an HL-7-compliant format inaccordance with the foregoing (and which could be directed to one ormore medical sub-systems 735 that require data in an HL-7-compliantformat).

The injection data management module 660 b may be characterized asincluding a first communication node 616 associated with the injectorcommunication bus 606, a second communication node 618 associated withthe first communication port 624, a communication node 618′ associatedwith the CMSDU communication port 628, and a communication node 618″associated with the RIS communication port 629. In the illustratedembodiment, the HIS 700 is able to send communications (e.g., a requestfor contrast administration data) to the injection data managementmodule 660 b through the second communication node 618 and the firstcommunication port 624. In one embodiment, the injection data managementmodule 660 b is configured so as to not allow communications from theHIS 700 to proceed past the first communication node 616 to the injectorcommunication bus 606 of the contrast media injector system 602. Thefirst communication port 624 of the injection data management module 660b may therefore be characterized as being of a pull-type configuration(e.g., contrast administration data may be “pulled” from the injectiondata management module 660 b by the HIS 700). Stated another way, theinjection data management module 660 b may be configured to transmitcontrast administration data to the HIS 700 only in response to arequest for contrast administration data submitted by the HIS 700 to theinjection data management module 660 b—the contrast media injectorsystem 602 does not automatically “push” contrast administration data tothe HIS 700 in this type of configuration. One or more processors 620 ofthe injection data management module 660 b may receive such a requestfor contrast administration data from the HIS 700, may retrieve therelevant contrast administration data from the data storage system 622of the injection data management module 660 b, and may transmit (orallow the transmission of) the retrieved contrast administration data tothe HIS 700 through the first communication port 624 of the injectiondata management module 660 b and communication link 674. In otherembodiments, the injection data management module 660 b may allow fortwo-way communication between the contrast media injector system 602 andthe HIS 700.

In one embodiment, the injection data management module 660 b isconfigured to send communications to the HIS 700 without first requiringa request or prompt from the HIS 700. In this regard, the firstcommunication port 624 of the injection data management module 660 b maybe characterized as being of a push-type configuration (e.g., contrastadministration data may be “pushed” from the injection data managementmodule 660 b to the HIS 700 on any appropriate basis). Stated anotherway, the injection data management module 660 b may be configured totransmit contrast administration data to the HIS 700 without firstrequiring a request for contrast administration data from the HIS 700(e.g., the contrast media injector system 602 may be configured toautomatically “push” contrast administration data to the HIS 700). Thecontrast media injector system 602 may be configured to transmitcontrast administration data to the HIS 700 on an automated orprogrammed basis, in response to user input provided to the injectiondata management module 660 b, or both. The injection data managementmodule 660 b may also be configured for push/pull communications inrelation to the HIS 700—the injection data management module 660 b maytransmit data to the HIS 700 in response to a request from the HIS 700,and the injection data management module 660 b may also be configured totransmit data to the HIS 700 on a programmed or automated basis.

The injection data management module 660 b includes a second dataconversion module 630 that is operatively interconnected with theinjector communication bus 606 of the contrast media injector system 602(e.g., via the communication link 672, which may actually be part of theinjector communication bus 606). Generally, the second data conversionmodule 630 converts contrast administration data between a firstCAN-compliant format (e.g., CAN 2.0A; associated with the injectorcommunication bus 606 of the contrast media injector system 602) and asecond CAN-compliant format (e.g., CiA 425; associated with the imagingsystem 690). This may be undertaken in any appropriate manner. Thesecond data conversion module 630 may be configured to provide for aconversion of commands that may be sent between the powerhead 604/remoteconsole 650 and the imaging system 690.

The second data conversion module 630 may utilize one or more processors620 of any appropriate type. One or more processors 620 may be used forthe data conversion provided by the second data conversion module 630.One or more processors 620 may be used to process requests for data(e.g., contrast administration data) received by the injection datamanagement module 660 b from the imaging system 690. Multiple processors620 may be arranged in any appropriate processing architecture forpurposes of the second data conversion module 630.

The second data conversion module 630 may utilize the data storagesystem 622 of the injection data management module 660 b. The datastorage system 622 may be arranged in any appropriate data storagearchitecture. Generally, data may be transmitted to the second dataconversion module 630 and stored on the data storage system 622 of theinjection data management module 660 b for use in conjunction withcommunications between the contrast media injector system 602 and theimaging system 690.

The injection data management module 660 b may be characterized asincluding a second communication port 638. The second communication port638 of the injection data management module 660 b is operativelyinterconnected with the imaging system 690 through the communicationlink 678. The injection data management module 660 b may becharacterized as including a first communication node 632 associatedwith the injector communication bus 606, and a second communication node634 associated with the second communication port 638. In oneembodiment, the injection data management module 660 b is configured toallow two-way communications between the contrast media injector system602 and the imaging system 690. For example, communications may be sentby the imaging system 690 to the contrast media injector system 602(e.g., the powerhead 604 thereof) through the injection data managementmodule 660 b (where the communication is converted from oneCAN-compliant format (e.g., CiA 425) to another CAN-compliant format(e.g., CAN 2.0A)) and communication link 672. Similarly, communicationsmay be sent from the contrast media injector system 602 (e.g., thepowerhead 604 thereof) to the imaging system 690 through thecommunication link 672, second data conversion module 630 (where thecommunication is converted from one CAN-compliant format (e.g., CAN2.0A) to another CAN-compliant format (e.g., CiA 425)) and communicationlink 678.

The injection data management module 660 b may include a third dataconversion module 640 that is operatively interconnected with theinjector communication bus 606 of the contrast media injector system 602(e.g., via the communication link 672, which may actually be part of theinjector communication bus 606). Generally, the third data conversionmodule 640 converts data (e.g., contrast administration data) from afirst CAN-compliant format (e.g., CAN 2.0A; associated with the injectorcommunication bus 606 of the contrast media injector system 602) to aPACS-compliant format (e.g., DICOM; associated with the PACS 710). Thismay be undertaken in any appropriate manner.

The third data conversion module 640 may utilize one or more processors620 of any appropriate type. One or more processors 620 may be used forthe data conversion provided by the third data conversion module 640.One or more processors 620 may be used by the injection data managementmodule 660 b to process requests for contrast administration datareceived by the injection data management module 660 b from the PACS710. Multiple processors 620 may be arranged in any appropriateprocessing architecture for purposes of the third data conversion module640.

The third data conversion module 640 may utilize the data storage system622 of the injection data management module 660 b. The data storagesystem 622 may be arranged in any appropriate data storage architecture.Generally, data may be transmitted to the third data conversion module640 and stored on the data storage system 622 for use in conjunctionwith communications between the contrast media injector system 602 andthe PACS 710.

The injection data management module 660 b may be characterized asincluding a PACS communication port 646. The PACS communication port 646of the injection data management module 660 b is operativelyinterconnected with the PACS 710 through the communication link 680. Theinjection data management module 660 b may be characterized as includinga first communication node 642 associated with the injectorcommunication bus 606, and a second communication node 644 associatedwith the PACS communication port 646. In one embodiment, the injectiondata management module 660 b is configured to allow two-waycommunications between the contrast media injector system 602 and thePACS 710. For example, communications may be sent by the PACS 710 to thecontrast media injector system 602 (e.g., the powerhead 604 thereof)through the injection data management module 660 b (where thecommunication is converted from a PACS-compliant format (e.g., DICOM) toa CAN-compliant format (e.g., CAN 2.0A)) and communication link 680.Similarly, communications may be sent from the contrast media injectorsystem 602 (e.g., the powerhead 604 thereof) to the PACS 710 through thecommunication link 672, third data conversion module 640 (where thecommunication is converted from a CAN-compliant format (e.g., CAN 2.0A)to a PACS-compliant format (e.g., DICOM)) and communication link 680.

The injection data management module 660 b may be of a “pull-type”configuration, as described herein, for communicating with the PACS 710(e.g., where the injection data management module 660 b transmits datato the PACS 710 only in response to a request from the PACS 710). Theinjection data management module 660 b may be of a “push-type”configuration, as described herein, for communicating with the PACS 710(e.g., where the injection data management module 660 b transmits datato the PACS 710 other than in response to a request from the PACS 710;where the contrast media injector system 602 and/or the injection datamanagement module 660 b are configured to transmit data to the PACS 710on an automated or programmed basis). The injection data managementmodule 660 b may be of a “push/pull-type” configuration, as describedherein, for communicating with the PACS 710. Data from the injectiondata management module 660 b may also be transmitted in response to userinput to the injection data management module 660 b.

The first data conversion module 614, second data conversion module 630,and third data conversion module 640 may be characterized as beinginterconnected in parallel (as opposed to being in series) in the FIG.19 configuration. Communications from the injector communication bus 606may be simultaneously directed to each of the first data conversionmodule 614, second data conversion module 630, and third data conversionmodule 640. The first data conversion module 614, second data conversionmodule 630, and third data conversion module 640 may be characterized asbeing part of a common structure or as being disposed within a commonhousing. The first data conversion module 614, the second dataconversion module 630, and the third data conversion module 640 may beincorporated by the injection data management module 660 b in asingle/common unit or may be distributed in any appropriate manner(e.g., in two or more units that are physically separate from oneanother).

FIG. 20 presents a functional schematic or block diagram of anotherconfiguration for the injection data management module 660 of thecontrast media injector system 602 of the medical system 600 of FIG.18A, and that is identified by reference numeral 660 c in FIG. 20.Corresponding components between the embodiments of FIGS. 19 and 20 areidentified by the same reference numeral. Those corresponding componentsthat differ in at least some respect are identified by a “single prime”designation in FIG. 20.

The injection data management module 660 c of FIG. 19 utilizes each ofthe above-discussed first data conversion module 614 and third dataconversion module 640, along with a modified second data conversionmodule 630′. Moreover, the injection data management module 660 c ofFIG. 20 utilizes a different arrangement of these components. Generally,the second data conversion module 630′ is connected in series with thefirst data conversion module 614, and is also connected in series withthe third data conversion module 640. As in the case of the FIG. 19embodiment, the first data conversion module 614 and third dataconversion module 640 of the injection data management module 660 c maybe connected in parallel.

The first data conversion module 614, the second data conversion module630′, and the third data conversion module 640 may be incorporated bythe injection data management module 660 c in a single/common unit. Forinstance, the injection data management module 660 c may be in the formof or as a component of a variation of the powerpack 246 discussed abovein relation to the power injector 240 of FIG. 1B (e.g., by its inclusionof a first data conversion module 614 and a third data conversion module640). An injection data management module 660 c in the form of asingle/common unit could also be physically separate from the powerpack246 of the type discussed above in relation to the power injector 240 ofFIG. 1B. A distributed architecture could also be used by the injectiondata management module 660 c (e.g., the injection data management module660 c may be implemented using two or more units that are physicallyseparate from one another, but that are operatively connected in themanner shown in FIG. 20). Any appropriate architecture may be used bythe injection data management module 660 c. The injection datamanagement module 660 c may also incorporate any one or more of thefeatures of the injection data management module 660 a discussed abovein relation to FIG. 18B.

The second data conversion module 630′ converts contrast administrationdata between a first CAN-compliant format (e.g., CAN 2.0A; associatedwith the injector communication bus 606 of the contrast media injectorsystem 602) and a second CAN-compliant format (e.g., CiA 425; associatedwith the imaging system 690). This data conversion may be undertaken inany appropriate manner. However, in the FIG. 20 configuration, theinjector communication bus 606 only communicates directly with thesecond data conversion module 630′ (and therefore the communication link672′ between the injection data management module 660 c and thepowerhead 604 uses the noted “single prime” designation—thecommunication link 672′ does not extend directly to either the firstdata conversion module 614 or the third data conversion module 640 inthe FIG. 20 configuration).

The contrast media injector system 602 and imaging system 690 continueto communicate through the second data conversion module 630′ in themanner discussed above for the FIG. 19 embodiment. However, in order toallow the injector communication bus 606 to also communicate with eachof the first data conversion module 614 and the third data conversionmodule 640, the second data conversion module 630′ includes a firstcommunication port 636 and a communication link 668. A secondcommunication node 634′ may be characterized as being associated withthe first communication port 636 of the second data conversion module630′.

The configuration and functionality of each of the first data conversionmodule 614 and the third data conversion module 640 in the FIG. 20embodiment remains in accordance with the FIG. 19 embodiment. However,contrast administration data may be transmitted from the injectorcommunication bus 606 through the first communication port 636 of theinjector data management module 660 c (where a conversion from oneCAN-compliant format to another CAN-compliant format occurs), and thenmay be transmitted over the communication link 668 to one or both of thefirst data conversion module 614 and the third data conversion module640 in the FIG. 20 configuration (where further conversions areundertaken in accordance with the foregoing).

One embodiment of a data management protocol 740 is presented in FIG.21, and may be utilized by the injection data management module 660 b ofFIG. 19. The contrast media injector system 602 may be operated (step742), for instance to execute a programmed injection where contrastmedia is injected into or administered to a patient (e.g., on at leastsomewhat of an automated basis) by the contrast media injector system602. Contrast administration data (e.g., data that relates in at leastsome manner to the execution of step 742) may be converted from a firstCAN-compliant format (e.g., CAN 2.0A) to a second CAN-compliant format(e.g., CiA 425) in accordance with step 744 (e.g., using the second dataconversion module 630 of FIG. 19). This converted data (step 744) may besent or transmitted to the imaging system 690 (e.g., via thecommunication link 678) at any appropriate time and in any appropriatemanner (step 746).

Contrast administration data (e.g., data on or pertaining to thecontrast media that is used in the execution of step 742, for instancecontrast-related data stored or to be stored in a data record 782 of adata structure 780, as discussed below in relation to FIGS. 23A-D, suchas one or more of the manufacturer, manufacturing date, lot number, NDCcode, composition, concentration, main functional ingredient(s), andexpiration date of the contrast media that was/is to be used in theexecution of step 742; contrast media volumes dispensed and/oradministered in relation to the execution of step 742; the flow rate(s)used in the administration of the contrast media) may be converted fromthe noted first CAN-compliant format to an HL-7-compliant formatpursuant to step 748 of the data management protocol 740 (e.g., usingthe first data conversion module 614 of FIG. 19). The conversionsassociated with steps 744 (e.g., CAN 2.0A to CiA 425) and 748 (e.g., CAN2.0A to HL-7) may be executed in any appropriate order, includingsimultaneously or where the execution of these steps at least partiallyoverlap. The converted data from step 748 (HL-7-compliant format) may bestored by the injection data management module 660 b in theHL-7-compliant format and in accordance with step 750 (e.g., stored bythe data storage system 622 of the injection data management module 660b).

The injection data management module 660 b may receive a request forcontrast administration data from the HIS 700 (step 752) in theexecution of the data management protocol 740. One or more processors620 of the injection data management module 660 b may assess thisrequest. The requested contrast administration data (step 752, which hasalready been converted from a CAN-compliant format to an HL-7-compliantformant) may be retrieved pursuant to step 754 (e.g., from the datastorage system 622 of the injection data management module 660 b usingone or more one or more processors 620). The retrieved contrastadministration data (step 754) may then be sent or transmitted to theHIS 700 pursuant to step 756 (e.g., via communication link 674). In a“push-type” configuration for the injection data management module 660b, step 752 of the protocol 740 may not be required. It should beappreciated that step 748 of the protocol 740 could be directed toconverting CAN-compliant data into PACS-compliant data (e.g., DICOM),and that this data could be transmitted from the injection datamanagement module 660 b (e.g., to PACS 710) pursuant to step 756.

One embodiment of a data management protocol 760 is presented in FIG.22, and may be utilized by the injection data management module 660 c ofFIG. 20. The contrast media injector system 602 may be operated (step762), for instance to execute a programmed injection where contrastmedia is injected into or administered to a patient (e.g., on at leastsomewhat of an automated basis) by the contrast media injector system602. Contrast administration data (e.g., data that relates in at leastsome manner to the execution of step 762) may be converted from a firstCAN-compliant format (e.g., CAN 2.0A) to a second CAN-compliant format(e.g., CiA 425) in accordance with step 764 (e.g., using the second dataconversion module 630′ of FIG. 20). This converted data (step 764) maybe sent or transmitted to the imaging system 690 (e.g., via thecommunication link 678) at any appropriate time and in any appropriatemanner (step 766).

Contrast administration data (e.g., data that relates in at least somemanner to the execution of step 762) may be converted from the notedsecond CAN-compliant format to an HL-7-compliant format pursuant to step768 of the data management protocol 760 (e.g., by transmittingCAN-compliant data from second data conversion module 630′ to the firstdata conversion module 614, where the first data conversion module 614converts this CAN-compliant data to HL-7-compliant data). Theconversions associated with steps 764 (e.g., CAN 2.0A to CiA 425) and748 (e.g., CiA 425 to HL-7) are executed in series in the case of thedata management protocol 760, with step 764 needing to be executed priorto step 768. The converted data from step 768 (HL-7-compliant format)may be stored by the injection data management module 660 c in theHL-7-compliant format and in accordance with step 770 (e.g., stored bythe data storage system 622 of the injection data management module 660c).

The injection data management module 660 c may receive a request forcontrast administration data from the HIS 700 (step 772) in theexecution of the data management protocol 760. One or more processors620 of the injection data management module 660 c may assess thisrequest. The requested contrast administration data (step 772, which hasalready been converted from a CAN-compliant format to an HL-7-compliantformant) may be retrieved pursuant to step 774 (e.g., from the datastorage system 622 of the injection data management module 660 c, usingone or more one or more processors 620 of the injection data managementmodule 660 c). The retrieved contrast administration data (step 774) maythen be sent or transmitted to the HIS 700 pursuant to step 776 (e.g.,via communication link 674). In a “push-type” configuration for theinjection data management module 660 c, step 772 of the protocol 760 maynot be required. It should be appreciated that step 768 of the protocol760 could be directed to converting CAN-compliant data intoPACS-compliant data (e.g., DICOM), and that this data could betransmitted from the injection data management module 660 c (e.g., toPACS 710) pursuant to step 776.

The medical system 600 of FIG. 18A may store various data relating toimaging and/or contrast media injection/administration operations. Oneembodiment of a data structure for storing data regarding the system 600is presented in FIGS. 23A-D and is identified by reference numeral 780.The data structure 780 includes a plurality of data records 782 (24 inthe illustrated embodiment). Any appropriate number of records 782 maybe stored in the data structure 780. The following fields may be used todefine a given data record 782 of the data structure 780, and data inthese various fields may be linked in any appropriate manner to definethe corresponding data record 782: a procedure date field 784 (e.g., thedate of a particular imaging operation (using the imaging system 690)where contrast media was administered to the patient (using the contrastmedia injector system 602)); an ICD9 code field 786 (e.g., a particularcode in the International Classification of Diseases); a patient IDfield 788 (e.g., any appropriate way of identifying the patient for thecorresponding imaging operation); a patient age field 790 (e.g., anumber that identifies the age of the patient for the correspondingimaging operation); a patient gender field 792 (e.g., any appropriateway of identifying the gender of the patient for the correspondingimaging operation); a patient weight field 794 (e.g., a number thatidentifies the weight of the patient for the corresponding imagingoperation); a patient height field 796 (e.g., a number(s) thatidentifies the height of the patient for the corresponding imagingoperation); a patient GFR field 798 (e.g., a number that identifies theglomerular filtration rate, estimated glomerular filtration rate, or thelike (e.g., some other metric that is representative of kidney or renalfunction) of the patient for the corresponding imaging operation)); areferring physician name field 800 (e.g., the name of the referringphysician for the corresponding imaging operation); a referringphysician ID field 802 (e.g., a number or code that identifies thereferring physician for the corresponding imaging operation); aprocedure location field 804 (e.g., a name, room/suite number, or codethat identifies a particular location for the corresponding imagingoperation); a modality field 806 (e.g., a name, number, or code thatidentifies the type of imaging technology that was used for thecorresponding imaging operation); a medical order ID field 808 (e.g., aname, number, or code that is associated with a particular medical orderfor the corresponding imaging operation); a procedure name field 810(e.g., a name, number, or code that identifies the patient region thatwas imaged by the corresponding imaging operation); a prescribedcontrast medium volume field 812 (e.g., a number that identifies thevolume of contrast media that was prescribed (e.g., by an attendingphysician) for use during the corresponding imaging operation); aprescribed contrast media concentration field 814 (e.g., a number thatidentifies the concentration of contrast media that was prescribed(e.g., by the attending physician) for use during the correspondingimaging operation); a prescribed contrast media flow rate field 816(e.g., a number that identifies the flow rate of contrast media that wasprescribed (e.g., by the attending physician) for use during thecorresponding imaging operation); a dispensed contrast media volumefield 818 (e.g., a number that identifies the volume of contrast mediathat was dispensed by the contrast media storage/dispensing unit 500 foruse during the corresponding imaging operation); a dispensed contrastmedia concentration field 820 (e.g., a number that identifies theconcentration of contrast media that was dispensed by the contrast mediastorage/dispensing unit 500 for use during the corresponding imagingoperation); a dispensed drug NDC field 822 (e.g., the National Drug Codefor the contrast media that was dispensed by the contrast mediastorage/dispensing unit 500 for use during the corresponding imagingoperation); a dispensed drug expiration date field 824 (e.g., a datethat identifies the expiration date of the drug that was dispensed bythe contrast media storage/dispensing unit 500 for use during thecorresponding imaging operation); an administered contrast media volumefield 826 (e.g., a number that identifies the volume of contrast mediathat was administered (injected) by the contrast media injector system602 for the corresponding imaging operation); an administered contrastmedia concentration field 828 (e.g., a number that identifies theconcentration of contrast media that was administered (injected) by thecontrast media injector system 602 during the corresponding imagingoperation); an administered contrast media flow rate field 830 (e.g., anumber that identifies the flow rate of contrast media that wasadministered (injected) by the contrast media injector system 602 duringthe corresponding imaging operation); a dispensed contrast media brandname field 831 (e.g., any way of identifying the brand name of thecontrast media that was dispensed by the contrast mediastorage/dispensing unit 500 for use during the corresponding imagingoperation); a dispensed contrast media manufacturer field 832 (e.g., anyway of identifying the manufacturer of the contrast media that wasdispensed by the contrast media storage/dispensing unit 500 for useduring the corresponding imaging operation); a dispensed contrast medialot number field 833 (e.g., any way of identifying the lot number of thecontrast media that was dispensed by the contrast mediastorage/dispensing unit 500 for use during the corresponding imagingoperation); a dispensed contrast media manufacture date field 834 (e.g.,any way of identifying the manufacturing date of the contrast media thatwas dispensed by the contrast media storage/dispensing unit 500 for useduring the corresponding imaging operation); a dispensed contrast mediacomposition field 835 (e.g., any way of identifying the composition ofthe contrast media that was dispensed by the contrast mediastorage/dispensing unit 500 for use during the corresponding imagingoperation); and a dispensed contrast media primary functional ingredientfield 836 (e.g., any way of identifying the primary functionalingredient (e.g., gadolinium, iodine, etc) of the contrast media thatwas dispensed by the contrast media storage/dispensing unit 500 for useduring the corresponding imaging operation).

One embodiment of an imaging protocol 840 is presented in FIG. 24, andmay be used by the medical system 600 of FIG. 18A. Patient informationmay be acquired pursuant to step 842 (e.g., for fields 786-798 of thedata structure 780). Physician information may be acquired pursuant tostep 844 (e.g., for fields 800, 802 of the data structure 780). Imagingprocedure information may be acquired pursuant to step 846 (e.g., forfields 804-810 of the data structure 780). Prescribed contrast mediainformation may be acquired pursuant to step 848. Information for eachof steps 842, 844, 846, and 848 may be acquired in any appropriate order(e.g., any sequence and/or simultaneous acquisition of information fromtwo or more steps) and in any appropriate manner, for instance from theHIS 700, via input to the medical system 600 in any appropriate manner(e.g., using the remote console 650 or a workstation 730; reading theinformation from a data storage device; from RIS 720; from PACS 710;from any other data system within the hospital).

A patient renal function check of some type may be undertaken at thecontrast media storage/dispensing unit 500 pursuant to step 850 of theimaging protocol 840. The patient renal function check of step 850 maybe in the form of the contrast medical storage/dispensing unit 500requiring that a confirmation be entered through a user input device 508of the unit 500, where this confirmation is that patient renal functionhas been checked. The patient renal function check of step 850 may be inthe form of the contrast medical storage/dispensing unit 500 requiringthat the patient's renal function be input to the unit 500 in anyappropriate manner (e.g., through a user input device 508 of the unit500; entry of patient information such that patent renal function datamay be retrieved from the HIS 700). The patient renal function that isinput to the contrast media storage/dispensing unit 500 may be comparedwith the threshold renal function of the contrast media to be dispensedfrom the contrast media storage/dispensing unit 500. If the patientrenal function information that has been input to the contrast mediastorage/dispensing unit 500 complies with the threshold renal functionof the contrast media to be dispensed from the contrast mediastorage/dispensing unit 500, the unit 500 may dispense the contrastmedia (step 852; e.g., in the form of a contrast media container 504being provided for use by the contrast media injector system 602 toinject/administer contrast media to a patient).

A patient renal function check of some type may also or alternatively beundertaken at the contrast media injector system 602 pursuant to step854 of the imaging protocol 840. The patient renal function check ofstep 854 may be in the form of the contrast media injector system 602requiring that a confirmation be entered through a user input device(e.g., via user input device 654 of the remote console 650; via userinput device 610 on the powerhead 604), where this confirmation is thatpatient renal function has been checked. The patient renal functioncheck of step 854 may be in the form of the contrast media injectorsystem 602 requiring that the patient's renal function be input to theinjector system 602 in any appropriate manner (e.g., via user inputdevice 654 of the remote console 650; via user input device 610 on thepowerhead 604; via entry of patient information such that patent renalfunction data may be retrieved from the HIS 700). The patient renalfunction that is input to the contrast media injector system 602 may becompared with the threshold renal function of the contrast media to beadministered from the contrast media injector system 602. Anyappropriate way of inputting the threshold renal function data to thecontrast media injector system 602 may be utilized (e.g., a user may berequired to input the threshold renal function to the contrast mediainjector system 602 though a user input device of the injector system602; the threshold renal function could be retrieved by the injectorsystem 602 from the corresponding contrast media container 504 providedby the contrast media storage/dispensing unit 500; the threshold renalfunction would be retrieved from the HIS 700). If the patient renalfunction information that has been input to the contrast media injectorsystem 602 complies with the threshold renal function of the contrastmedia to be administered (injected) by the contrast media injectorsystem 602, the injector system 602 may be operated pursuant to step 856to administer/inject contrast media into the patient (e.g., viaexecution of a programmed injection).

The injector system 602 (step 856) and imaging device system 690 (step858) may be operated in any appropriate manner to acquire a desiredimage/images of the patient undergoing the imaging procedure. Step 860of the imaging protocol 840 is directed to acquiring contrastadministration data (e.g., relating at least in some manner to theoperation of the contrast media injector system 602). At least some ofthe contrast administration data may be converted from one format toanother format pursuant to step 862 of the imaging protocol 840 (e.g.,in accordance with FIGS. 19-22 above), and this converted contrastadministration data may be stored pursuant to step 864 of the imagingprotocol 840 (e.g., in the data structure 780). This converted contrastadministration data may be used in any appropriate manner, for instancefor electronic records purposes; for inventory tracking purposes; forbilling purposes; for use by or in relation to laboratory informationsystems; medication and procedure error tracking; quality controls;contrast media usage reporting; documentation of drug dispense andadministration; documentation of patient exposure to radiation and/oriodine; patient outcomes analyses; departmental reporting; and contrastusage analysis and reporting.

Any of the modules, protocols, logic, or the like addressed herein maybe implemented in any appropriate manner, including without limitationin any appropriate software, firmware, or hardware, using one or moreplatforms, using one or more processors, using memory of any appropriatetype, using any single computer of any appropriate type or multiplecomputers of any appropriate type and interconnected in any appropriatemanner, or any combination thereof. These modules, protocols, logic, orthe like may be implemented at any single location or at multiplelocations that are interconnected in any appropriate manner (e.g., viaany type of network).

The foregoing description of the present invention has been presentedfor purposes of illustration and description. Furthermore, thedescription is not intended to limit the invention to the form disclosedherein. Consequently, variations and modifications commensurate with theabove teachings, and skill and knowledge of the relevant art, are withinthe scope of the present invention. The embodiments describedhereinabove are intended to explain best modes known of practicing theinvention and to enable others skilled in the art to utilize theinvention in such, or other embodiments and with various modificationsrequired by the particular application(s) or use(s) of the presentinvention. It is intended that the appended claims be construed toinclude alternative embodiments to the extent permitted by the priorart.

1. A contrast media injector system comprising: a powerhead comprising:a housing; a motorized drive ram designed to move along an axis, whereinat least a portion of said motorized drive ram is located within saidhousing; and a syringe mount designed to at least substantiallyimmobilize a barrel of a syringe relative to said housing such that saiddrive ram can move a plunger of the syringe within and relative to thebarrel of the syringe; a first console in communication with saidpowerhead, wherein said first console comprises a first display, andwherein said first console can be utilized by a user to programinjection parameters; a power injector control module comprising aCAN-compliant injector communication bus; and a first data conversionmodule operatively interconnected with said CAN-compliant injectorcommunication bus, wherein said first data conversion module isconfigured to convert CAN-compliant data from said CAN-compliantinjector communication bus to HL-7-compliant data.
 2. The contrast mediainjector system of claim 1, further comprising: a second data conversionmodule operatively interconnected with said CAN-compliant injectorcommunication bus, and wherein said second data conversion module isconfigured to convert CAN-compliant data from said CAN-compliantinjector communication bus from a first CAN-compliant format to a secondCAN-compliant format.
 3. The contrast media injector system of claim 2,wherein said second CAN-compliant format comprises CiA
 425. 4. Thecontrast media injector system of claim 2, wherein said first and seconddata conversion modules are connected in parallel.
 5. The contrast mediainjector system of claim 3, wherein said first data conversion moduleconverts data from said first CAN-compliant format to saidHL-7-compliant data.
 6. The contrast media injector system of claim 2,wherein said first and second data conversion modules are connected inseries.
 7. The contrast media injector system of claim 2, wherein saidfirst data conversion module converts data from said secondCAN-compliant format to said HL-7-compliant data.
 8. A medical datamanagement system comprising an imaging system, a medical informationsystem, and the contrast media injector system of claim 2, wherein saidfirst data conversion module is operatively interconnected with saidmedical information system, and wherein said second data conversionmodule is operatively interconnected with said imaging system.
 9. Themedical data management system of claim 8, wherein said medicalinformation system comprises a hospital information system.
 10. Thecontrast media injector system of claim 2, further comprising: a firsthousing, wherein said second data conversion module is disposed withinsaid first housing; and a communication link between said second dataconversion module and said powerhead.
 11. The contrast media injectorsystem of claim 10, wherein said first data conversion module isdisposed within said first housing.
 12. The contrast media injectorsystem of claim 11, wherein said first housing comprises first andsecond communication ports, wherein said first communication port isoperatively interconnected with said first data conversion module, andwherein said second communication port is operatively interconnectedwith said second data conversion module.
 13. A medical system comprisingan imaging system, a medical information system, and the contrast mediainjector system of claim 12, wherein said first data conversion moduleis operatively interconnected with said medical information systemthrough said first communication port, and wherein said second dataconversion module is operatively interconnected with said imaging systemthrough said second communication port.
 14. The medical system of claim13, wherein said medical information system comprises a hospitalinformation system.
 15. The contrast media injector system of claim 10,wherein said first data conversion module is located outside of saidfirst housing, wherein said first housing comprises first and secondcommunication ports each operatively interconnected with said seconddata conversion module, and wherein said first data conversion module isoperatively interconnected with said second data conversion modulethrough first communication port.
 16. The contrast media injector systemof claim 15, further comprising: a wired communication link between saidfirst communication port and said first data conversion module.
 17. Amedical system comprising an imaging system, a medical informationsystem, and the contrast media injector system of claim 15, wherein saidmedical information system is operatively interconnected with said firstcommunication port of said second data conversion module through saidfirst data conversion module, and wherein said second data conversionmodule is operatively interconnected with said imaging system throughsaid second communication port.
 18. The contrast media injector systemof claim 1, wherein said first data conversion module comprises firstand second communication nodes, wherein said first communication node isoperatively interconnected with said CAN-compliant injectorcommunication bus, wherein there is only one-way communication betweensaid CAN-compliant injector communication bus and said secondcommunication node through said first communication node, and whereinsaid first data conversion module accommodates two-way communicationthrough said second communication node.
 19. The contrast media injectorsystem of claim 1, wherein said first data conversion module comprisesfirst and second communication nodes, wherein said first communicationnode is operatively interconnected with said CAN-compliant injectorcommunication bus, and wherein said first data conversion modulecomprises a pull-type data transfer configuration in relation to saidsecond communication node.
 20. The contrast media injector system ofclaim 1, wherein said first data conversion module comprises first andsecond communication nodes, wherein said first communication node isoperatively interconnected with said CAN-compliant injectorcommunication bus, and wherein said first data conversion module isconfigured to output data to said second communication node only inresponse to a data request received by said first data conversion modulethrough said second communication node.
 21. A medical system comprisinga medical information system and the contrast media injector system ofclaim 18, wherein said first data conversion module is operativelyinterconnected with said medical information system through said secondcommunication node.
 22. The medical system of claim 21, wherein saidmedical information system comprises a hospital information system. 23.A medical system, comprising: a contrast media injector systemcomprising a reader and an injector communication bus; an imaging systemoperatively interconnected with said contrast media injector system; afirst console comprising a first display and a first user input device,wherein said first console is operatively interconnected with at leastone of said contrast media injector system and said imaging system; acontrast media storage/dispensing unit comprising a plurality ofcontrast media containers, wherein each said contrast media containercomprises a data storage device, and wherein said reader is operable toat least read data from said data storage device of a corresponding saidcontrast media container having contrast media to be used by saidcontrast media injector system; a medical information system; and aninjection data management module comprising a first data conversionmodule, wherein said injection data management module is disposedbetween and operatively interconnected with each of said injectorcommunication bus and said medical information system.
 24. (canceled)25. A medical system, comprising: a contrast media injector systemcomprising an injector communication bus; an imaging system operativelyinterconnected with said contrast media injector system; a first consolecomprising a first display and a first user input device, wherein saidfirst console is operatively interconnected with at least one of saidcontrast media injector system and said imaging system; a contrast mediastorage/dispensing unit comprising a plurality of contrast mediacontainers; at least one renal function assessment module; a medicalinformation system; and an injection data management module comprising afirst data conversion module, wherein said injection data managementmodule is disposed between and operatively interconnected with each ofsaid injector communication bus and said medical information system.26-50. (canceled)